This file contains important information on the products of the SIMATIC NET PC‑Software‑CD 11/2003 for Windows XP, Windows 2000, and Windows Server 2003.

The version number of the SIMATIC NET PC Software CD 11/2003 Products is V6.2.

The SIMATIC NET PC Software CD 11/2003 replaces the SIMATIC NET PC Software CD 11/2002 + SP1.

The first sections deal with the SIMATIC NET products (Section 1 through 22) and these are followed by general topics.

Please read the section relevant to your product carefully. If there are other sections that are important for a product, this will be pointed out in the product sections themselves.

Contents

1 Communications processor CP 5613, CP 5613 FO, CP 5614, CP 5614 FO, CP 5613 A2, CP 5614 A2

2 DP-5613

3 S7-5613

4 FMS-5613

5 CP 5511 Communications Processor

6 CP 5512 Communications Processor

7 CP 5611/CP 5611 MPI Communications Processor

8 SOFTNET-S7 (for PROFIBUS)

9 SOFTNET-DP (for PROFIBUS)

10 SOFTNET-DP Slave (for PROFIBUS)

11 CP 1613 Communications Processor

12 S7-1613

13 PG-1613

14 TF-1613

15 S7-REDCONNECT and S7-REDCONNECT Upgrade

16 CP 1512 Communications Processor

17 CP 1612 Communications Processor

18 SOFTNET-S7 for Industrial Ethernet

19 SOFTNET-S7 Lean for Industrial Ethernet

20 SOFTNET-PG for Industrial Ethernet

21 PROFInet OPC Server

22 SNMP OPC Server

23 DX OPC Server

24 Requirements and Restrictions Relating to Supported Windows Operating Systems

25 Information, Restrictions and Notes Relating to OPC

26 Notes on Licenses and Key Diskettes

27 Requirements and Restrictions Relating to Hardware in General

28 Compatibility

29 Notes on C Programming Interfaces

30 Notes on Configuration, Configuring and NCM

31 Examples of C Programming Interfaces

32 Development Environments and Compilers Supported

33 Routing

1 Communications processor CP 5613, CP 5613 FO, CP 5614, CP 5614 FO, CP 5613 A2, CP 5614 A2

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to the Supported Windows Operating Systems "

· Section 25 "Information, Restrictions, and Notes on OPC "

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 29 "Notes on C Programming Interfaces"

· Section 30 "Notes on Configuration, Configuring and NCM"

You only need to read the other sections if they relate directly to your product.

The electronic version of the Installation Instructions and other SIMATIC NET documents can be found on the accompanying SIMATIC NET CD "Manual Collection" (electronic manuals) or in the download version in separate files that can be downloaded from the Web.
If you install the SIMATIC NET PC software products under Windows Server 2003, certification messages are displayed. Please confirm the messages. Otherwise the installation will be canceled.

The following CP 5613 names refer to the communications processors CP 5613, CP 5613 FO, CP 5614, CP 5614 FO, CP 5613 A2, CP 5614 A2 unless special types are named explicitly.

1.1 Version History

Version	Changes/Additionally Supported Functions
V6.2	· Windows 2000 + SP4 is supported. · Windows Server 2003 is supported. · Support for the new modules CP 5613 A2 and CP 5614 A2
V6.1.1	Windows 2000 is supported on the same CD as Windows XP.
V6.1	Windows XP is supported.
V6.0.5 HF2	· V6.0.5 Hotfix 2 also contains Hotfix 1. · WinCC Version 5.1, along with SIMATIC NET V6.0.5, can only be used with Hotfix 2.
V6.0.5	· Multiterminal capability · Support of DP-V1 functions on the slave submodule (CP 5614).
V6.0	New, uniform configuration with SIMATIC NCM PC or STEP 7 instead of with lots of tools (COML S7, COM PB).
V2.1.2	Corrections for DP applications
V2.1	· Windows 2000 Professional is supported. · FMS · Constant bus cycle time mode - the constant bus cycle parameters are set in STEP 7/NCM V5.1.
V2.0	· Properties and diagnostics can be set using the "Set PG/PC Interface" configuration program as with other SIMATIC NET modules. · Extended diagnostic functionality · The FDL programming interface is supported. · PG functionality · Support of the trace in the slave submodule · Up to four CP 5613/CP 5614 modules at the same time · DPC1 (version 1.13, as for CP 5412 (A2) V5.0 or higher) · DPC2 · FDL · S7 · Support of STEP 7, version 5.0, from service pack 3 onwards · Support of PG functionality with STEP 5 and STEP 7
V1.2	· Support of Fast Logic functionality · Slave properties of the CP 5614 · User watchdog for DP master (not for slave functions) · Use of more than one CP 5613/CP 5614 at the same time · Use of one CP 5613/CP 5614 by several application programs at the same time
V1.1	Slave functions and transfer mechanism of the CP 5614
V1.0	Base version

1.2 General Information

Communication partners

The DP master of the CP 5613 can be operated with certified DP slaves.

The DP slave of the CP 5614 can be operated with certified DP master stations.

Parallel operation of protocols

A maximum of two protocols can be operated at the same time, for example PROFIBUS DP and PROFIBUS FMS.

Supported data transmission rates

· 9.6 Kbps

· 19.2 Kbps

· 45.45 Kbps

· 93.75 Kbps

· 187.5 Kbps

· 500.0 Kbps

· 1.5 Mbps

· 3.0 Mbps

· 6.0 Mbps

· 12.0 Mbps

Parallel operation of the CP 5613

Up to four CP 5613 modules can be operated at the same time.

Bus parameters for a DP slave

The DP slave section of the CP 5614 can adapt itself to the bus parameters of the attached network.

1.3 Restrictions

Incompatibility with certain PC types

The CP 5613/CP 5614 does not work on a Celsius 620 computer with Tyan 100 motherboard

This problem has been fixed from hardware version 03 of the CP (mid 2000).

FDL programming interface

The FDL-IDENT service is not supported.

Uninstalling / deactivating CPs using the Device Manager

Configured CPs must not be uninstalled/deactivated using the Device Manager.

Hot plugging

The communications processors CP 5613, CP 5613 FO, CP 5614, CP 5614 FO, CP 5613 A2, CP 5614 A2 are not released for hot plugging.

PowerPG with CP 5613 A2/CP 5614 A2

Please note that you can only operated one CP 5613 A2 or CP 5614 A2 communications processor in a PowerPG with Windows 2000 and Windows 2000 Server.

Multiboard operation

No multiboard mode is possible with DPC2.

1.4 Notes on Commissioning

If the Plug-and-Play mechanism does not find the driver after installing the CP and then rebooting the computer, the computer must be forced to find the driver at the instigation of the user.

Follow the steps below:

1. Restart your computer.

2. Go to the Device Manager (taskbar Start -> Control Panel -> System -> Hardware tab -> Device Manager button).

3. In the "Device Manager" dialog, click the "Scan for hardware changes "button in the menu bar.

4. Confirm all the following dialogs with "Next".

Bus collisions after reinstallation

If two CP 5613 communications processors are installed in one computer, when the computer starts up, both communication modules are assigned bus address 0. This causes collisions if both modules are connected to the same bus.

Remedy: Set different bus addresses for the communications processors before attaching to the bus.

1.5 Notes on Configuration and Configuring

Installing a CP 5613 after installing the SIMATIC NET CD

If a CP 5613 is installed in the computer after you have installed the SIMATIC NET Software Product CD, the module is not always installed automatically after you restart the PC. Instead, the Hardware Manager or its Wizard for new hardware appears. You can then install the CP here (by clicking the buttons "Next" and "Finish" one after the other).

Properties Page in the Station Configuration Editor

In the properties page of the Station Configuration Editor, only fixed PROFIBUS bus profiles can be created for node initialization.

User-specific bus parameters for large network spans and networks such as redundant OLM rings can be specified with the "Configuration Console" tool.

You can start this software tool from the Windows Start menu -> SIMATIC -> SIMATIC NET -> Settings.

Configuring the CP 5614/CP 5614 FO/CP 5614 A2 as a slave

It is currently only possible to configure the CP 5614/CP 5614 FO/CP 5614 A2 as a slave using GSD files. If necessary, you can orient yourself on two sample files for the CP 5614/CP 5614/CP 5614 A2 that are copied to the SIMATIC.NET\DP\DEMO_GSD folder when you install software. You can import these files in SIMATIC NCM PC/STEP 7 and change their configuration accordingly.

If you require the Ident number of the slave, you can take this from the relevant GSD file.

Inserting/removing CP 5613 communications processors

If you insert a further CP 5613 communications processor or remove an inserted CP 5613, all configured CP 5613 modules are removed from the Station Manager. You may need to reconfigure the modules in the computer.

Configuration limits and performance data of the modules

You will find the configuration limits and performance data of the modules on the Siemens Web pages as FAQs under entry ID 15227599.

· German link: http://www4.ad.siemens.de/view/cs/de/15227599

· English link: http://www4.ad.siemens.de/view/cs/en/15227599

Bus parameters

When using PG operation, please note that if the bus parameters are incorrectly set, you must reset and restart with the "Set PG/PC Interface" program or Configuration Console after correcting the bus parameters.

Downloading a configuration for the CP 5613/CP 5614 to a compatible CP 5613/ CP 5614 A2

Downloading a configuration for the CP 5613/CP 5614 to a compatible CP 5613/ CP 5614 A2 is only possible with a local or remote download. The CP must first be inserted in the Station Configuration Editor.

2 DP-5613

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to Supported Windows Operating Systems"

· Section 25 "Information, Restrictions and Notes Relating to OPC"

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 29 "Notes on C Programming Interfaces"

· Section 30 "Notes on Configuration, Configuring and NCM"

You only need to read the other sections if they relate directly to your product.

The following CP 5613 names refer to the communications processors CP 5613, CP 5613 FO, CP 5614, CP 5614 FO, CP 5613 A2, CP 5614 A2 unless special types are named explicitly.

2.1 Version History

Version	Changes/Additionally Supported Functions
V6.2	· Windows 2000 + SP4 is supported. · Windows Server 2003 is supported. · Support for the new modules CP 5613 A2 and CP 5614 A2
V6.1.1	Windows 2000 is supported on the same CD as Windows XP.
V6.1	Windows XP is supported.
V6.0.5 HF2	· V6.0.5 Hotfix 2 also contains Hotfix 1. · WinCC Version 5.1, along with SIMATIC NET V6.0.5, can only be used with Hotfix 2.
V6.0.5	· Multiterminal capability · Support of DP-V1 functions on the slave submodule (CP 5614)
V6.0	New, uniform configuration with SIMATIC NCM PC or STEP 7 instead of with lots of tools (COML S7, COM PB)
V2.1.3	Corrections for WinLC applications
V2.1.2	Corrections for DP applications
V2.1	Windows 2000 Professional is supported
V2.0	· Properties and diagnostics can be set using the "Set PG/PC Interface" configuration program as with other SIMATIC NET modules · Extended diagnostic functionality · The FDL programming interface is supported · PG functionality · Full support of the DP programming interface as with the CP 5412 (A2) module.
V1.0	Base version

2.2 Restrictions

No parallel operation of the DP-Base and DP-Lib programming interfaces

The DP-5613 product contains the DP-Lib programming interface and several programs for testing the functionality of this interface.

Please note that it is not possible to use this interface and the DP Base programming interface included in the "CP 5613/CP 5614 (DP-Base)" product on one CP at the same time. Although it is possible to install both products at the same time, you can only run programs that use one of these interfaces at the same time on one CP.

The "DP_get_pointer" function call returns timeout during simultaneous operation with the DP OPC server

The DP OPC server uses the powerful DP Base interface for communication. When operating the DP OPC server at the same time as a DP slave user program for the slave part of the CP 5614/CP 5614 FO, calling the DP_get_pointer function returns a timeout after approximately 10 seconds.

Global control different from the CP 5412 (A2)

The DP interface of the CP 5613 differs slightly in its dynamics and functionality from that of the CP 5412 (A2): Cyclic, global control frames that could be configured with COM PROFIBUS for the CP 5412 (A2) are not supported by the CP 5613).

FDL programming interface

The FDL-IDENT service is not supported.

Hot plugging

The communications processors CP 5613, CP 5613 FO, CP 5614, CP 5614 FO, CP 5613 A2, CP 5614 A2 are not released for hot plugging.

PowerPG with CP 5613 A2/CP 5614 A2

Please note that you can only operated one CP 5613 A2 or CP 5614 A2 communications processor in a PowerPG with Windows 2000 and Windows 2000 Server.

Receiving bus parameters

Receiving bus parameters is supported only by the "Set PG/PC Interface" program.

Multiboard operation

No multiboard mode is possible with DPC2.

2.3 Notes on Commissioning

If the Plug-and-Play mechanism does not find the driver after installing the CP and then rebooting the computer, the computer must be forced to find the driver at the instigation of the user.

Follow the steps below:

1. Restart your computer.

2. Go to the Device Manager (taskbar Start -> Control Panel -> System -> Hardware tab -> Device Manager button).

3. In the "Device Manager" dialog, click the "Scan for hardware changes "button in the menu bar.

4. Confirm all the following dialogs with "Next".

Bus collisions after reinstallation

Remedy: Set different bus addresses for the communications processors before attaching to the bus.

2.4 Notes on Configuration and Configuring

Installing a CP 5613 after installing the SIMATIC NET CD

If a CP 5613 is installed in the computer after you have installed the SIMATIC NET Software Product CD, the module is not always installed automatically after you restart the PC. Instead, the Hardware Manager opens. You can then install the CP here (by clicking the buttons "Next" and "Finish" one after the other).

Properties Page in the Station Configuration Editor

In the properties page of the Station Configuration Editor, only fixed PROFIBUS bus profiles can be created for node initialization.

User-specific bus parameters for large network spans and networks such as redundant OLM rings can be specified with the "Configuration Console" tool.

You can start this software tool from the Windows Start menu -> SIMATIC -> SIMATIC NET -> Settings.

DP master class 2 services (DPMCL2 programming interface)

If you use DP master class 2 services, you must modify the master address of the database with the dp_mcl2_init( ) call.

Inserting/removing CP 5613 communications processors

Bus parameters

Downloading a configuration for the CP 5613/CP 5614 to a compatible CP 5613/ CP 5614 A2

CP 5613 as MPI interface

If a CP 5613 is used as an MPI interface, remember that the PROFIBUS profile is activated automatically if no further access point is mapped to the MPI profile (keep this in mind when S7ONLINE is mapped to PC internal (local)).

3 S7-5613

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to Supported Windows Operating Systems"

· Section 25 "Information, Restrictions and Notes Relating to OPC"

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 29 "Notes on C Programming Interfaces "

· Section 30 "Notes on Configuration, Configuring and NCM"

You only need to read the other sections if they relate directly to your product.

The following CP 5613 names refer to the communications processors CP 5613, CP 5613 FO, CP 5614, CP 5614 FO, CP 5613 A2, CP 5614 A2 unless special types are named explicitly.

3.1 Version History

Version	Changes/Additionally Supported Functions
V6.2	· Windows 2000 + SP4 is supported. · Windows Server 2003 is supported. · Support for the new modules CP 5613 A2 and CP 5614 A2
V6.1.1	Windows 2000 is supported on the same CD as Windows XP.
V6.1	Windows XP is supported.
V6.0.5 HF2	· V6.0.5 Hotfix 2 also contains Hotfix 1. · WinCC Version 5.1, along with SIMATIC NET V6.0.5, can only be used with Hotfix 2.
V6.0.5	Multiterminal capability
V6.0	New, uniform configuration with SIMATIC NCM PC or STEP 7 instead of with lots of tools (COML S7, COM PB)
V2.1.1	Corrections for PCS 7 applications
V2.1	Windows 2000 Professional is supported
V2.0	Base version

3.2 Restrictions

Hot plugging

The communications processors CP 5613, CP 5613 FO, CP 5614, CP 5614 FO, CP 5613 A2, CP 5614 A2 are not released for hot plugging.

PowerPG with CP 5613 A2/CP 5614 A2

Please note that you can only operated one CP 5613 A2 or CP 5614 A2 communications processor in a PowerPG with Windows 2000 and Windows 2000 Server.

Receiving bus parameters

Receiving bus parameters is supported only by the "Set PG/PC Interface" program.

3.3 Notes on Commissioning

If the Plug-and-Play mechanism does not find the driver after installing the CP and then rebooting the computer, the computer must be forced to find the driver at the instigation of the user.

Follow the steps below:

1. Restart your computer.

2. Go to the Device Manager (taskbar Start -> Control Panel -> System -> Hardware tab -> Device Manager button).

3. In the "Device Manager" dialog, click the "Scan for hardware changes "button in the menu bar.

4. Confirm all the following dialogs with "Next".

Bus collisions after reinstallation

Remedy: Set different bus addresses for the communications processors before attaching to the bus.

3.4 Notes on Configuration and Configuring

Installing a CP 5613 after installing the SIMATIC NET CD

If a CP 5613 is installed in the computer after you have installed the SIMATIC NET Software Product CD, the module is not always installed automatically after you restart the PC. Instead, the Hardware Manager opens. You can then install the CP here (by clicking the buttons "Next" and "Finish" one after the other).

Properties Page in the Station Configuration Editor

In the properties page of the Station Configuration Editor, only fixed PROFIBUS bus profiles can be created for node initialization.

User-specific bus parameters for large network spans and networks such as redundant OLM rings can be specified with the "Configuration Console" tool.

You can start this software tool from the Windows Start menu -> SIMATIC -> SIMATIC NET -> Settings.

Inserting/removing CP 5613 communications processors

Configuration limits and performance data of the modules

You will find the configuration limits and performance data of the modules on the Siemens Web pages as FAQs under entry ID 15227599.

· German link: http://www4.ad.siemens.de/view/cs/de/15227599

· English link: http://www4.ad.siemens.de/view/cs/en/15227599

Bus parameters

Downloading a configuration for the CP 5613/CP 5614 to a compatible CP 5613/ CP 5614 A2

CP 5613 as MPI interface

4 FMS-5613

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to Supported Windows Operating Systems"

· Section 25 "Information, Restrictions and Notes Relating to OPC"

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 29 "Notes on C Programming Interfaces"

· Section 30 "Notes on Configuration, Configuring and NCM"

You only need to read the other sections if they relate directly to your product.

The following CP 5613 names refer to the communications processors CP 5613, CP 5613 FO, CP 5614, CP 5614 FO, CP 5613 A2, CP 5614 A2 unless special types are named explicitly.

4.1 Version History

Version	Changes/Additionally Supported Functions
V6.2	· Windows 2000 + SP4 is supported. · Windows Server 2003 is supported. · Support for the new modules CP 5613 A2 and CP 5614 A2
V6.1.1	Windows 2000 is supported on the same CD as Windows XP.
V6.1	Windows XP is supported.
V6.0.5 HF2	· V6.0.5 Hotfix 2 also contains Hotfix 1. · WinCC Version 5.1, along with SIMATIC NET V6.0.5, can only be used with Hotfix 2.
V6.0.5	Multiterminal capability
V6.0	New, uniform configuration with SIMATIC NCM PC or STEP 7 instead of with lots of tools (COML S7, COM PB).
V2.1.1	Base version

4.2 Notes on Commissioning

If the Plug-and-Play mechanism does not find the driver after installing the CP and then rebooting the computer, the computer must be forced to find the driver at the instigation of the user.

Follow the steps below:

1. Restart your computer.

2. Go to the Device Manager (taskbar Start -> Control Panel -> System -> Hardware tab -> Device Manager button).

3. In the "Device Manager" dialog, click the "Scan for hardware changes "button in the menu bar.

4. Confirm all the following dialogs with "Next".

Bus collisions after reinstallation

Remedy: Set different bus addresses for the communications processors before attaching to the bus.

4.3 Restrictions

Always access protection for FMS variables

When a connection is established, both FMS partners send information indicating whether or not access protection for their variables is supported. The PC end always indicates "no access protection supported" even if access protection was configured. Illegal read or write access is, however, rejected by the PC end.

Multithread operation

Please note that the fms_receive( ) call and the corresponding processing function run in the same thread.

Hot plugging

The communications processors CP 5613, CP 5613 FO, CP 5614, CP 5614 FO, CP 5613 A2, CP 5614 A2 are not released for hot plugging.

PowerPG with CP 5613 A2/CP 5614 A2

Please note that you can only operated one CP 5613 A2 or CP 5614 A2 communications processor in a PowerPG with Windows 2000 and Windows 2000 Server.

Receiving bus parameters

Receiving bus parameters is supported only by the "Set PG/PC Interface" program.

4.4 Notes on Configuration and Configuring

Installing a CP 5613 after installing the SIMATIC NET CD

If a CP 5613 is installed in the computer after you have installed the SIMATIC NET Software Product CD, the module is not always installed automatically after you restart the PC. Instead, the Hardware Manager opens. You can then install the CP here (by clicking the buttons "Next" and "Finish" one after the other).

Properties Page in the Station Configuration Editor

In the properties page of the Station Configuration Editor, only fixed PROFIBUS bus profiles can be created for node initialization.

User-specific bus parameters for large network spans and networks such as redundant OLM rings can be specified with the "Configuration Console" tool.

You can start this software tool from the Windows Start menu -> SIMATIC -> SIMATIC NET -> Settings.

Inserting/removing CP 5613 communications processors

Configuration limits and performance data of the modules

You will find the configuration limits and performance data of the modules on the Siemens Web pages as FAQs under entry ID 15227599.

· German link: http://www4.ad.siemens.de/view/cs/de/15227599

· English link: http://www4.ad.siemens.de/view/cs/en/15227599

Bus parameters

Downloading a configuration for the CP 5613/CP 5614 to a compatible CP 5613/ CP 5614 A2

CP 5613 as MPI interface

5 CP 5511 Communications Processor

Please read the Installation Instructions supplied in paper form with the CP 5511.

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to Supported Windows Operating Systems"

· Section 25 "Information, Restrictions and Notes Relating to OPC"

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 29 "Notes on C Programming Interfaces"

· Section 30 "Notes on Configuration, Configuring and NCM"

You only need to read the other sections if they relate directly to your product.

5.1 Restrictions

No multiprocessor system

The CP 5511 is not approved for operation in a PC with a multiprocessor system, for example double Pentium.

Operation with a PC with hyperthreading is also not released because it has not been tested.

Restriction with notebooks

The CP 5511 has not been released for the Compaq Armada 110 notebook.

Restriction with SIMATIC Power PG

The CP 5511 can only be plugged into the front slot of the SIMATIC Power PG (the slot next to the screen).

5.2 Notes on Commissioning

If the Plug-and-Play mechanism does not find the driver after installing the CP and then rebooting the computer, the computer must be forced to find the driver at the instigation of the user.

Follow the steps below:

1. Restart your computer.

2. Go to the Device Manager (taskbar Start -> Control Panel -> System -> Hardware tab -> Device Manager button).

3. In the "Device Manager" dialog, click the "Scan for hardware changes "button in the menu bar.

4. Confirm all the following dialogs with "Next".

5.3 Notes on Configuration and Configuring

Properties Page in the Station Configuration Editor

In the properties page of the Station Configuration Editor, only fixed PROFIBUS bus profiles can be created for node initialization.

User-specific bus parameters for large network spans and networks such as redundant OLM rings can be specified with the "Configuration Console" tool.

You can start this software tool from the Windows Start menu -> SIMATIC -> SIMATIC NET -> Settings.

Operation in the PG 750 PIII

When operating the CP 5511 in the PG 750 PIII, set the BIOS option CARDBUS/PCMCIA slot to "enable" prior to installation.

6 CP 5512 Communications Processor

Please read the Installation Instructions supplied in paper form with the CP 5512.

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to Supported Windows Operating Systems "

· Section 25 "Information, Restrictions and Notes Relating to OPC"

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 29 "Notes on C Programming Interfaces"

· Section 30 "Notes on Configuration, Configuring and NCM"

You only need to read the other sections if they relate directly to your product.

6.1 Restrictions

No multiprocessor system

The CP 5512 is not approved for operation in a PC with a multiprocessor system, for example double Pentium.

Operation with a PC with hyperthreading is also not released because it has not been tested.

6.2 Notes on Commissioning

Starting the Plug-and-Play mechanism manually

If the Plug-and-Play mechanism does not find the driver after installing the CP and then rebooting the computer, the computer must be forced to find the driver at the instigation of the user.

Follow the steps below:

1. Restart your computer.

2. Go to the Device Manager (taskbar Start -> Control Panel -> System -> Hardware tab -> Device Manager button).

3. In the "Device Manager" dialog, click the "Scan for hardware changes "button in the menu bar.

4. Confirm all the following dialogs with "Next".

Properties Page in the Station Configuration Editor

In the properties page of the Station Configuration Editor, only fixed PROFIBUS bus profiles can be created for node initialization.

User-specific bus parameters for large network spans and networks such as redundant OLM rings can be specified with the "Configuration Console" tool.

You can start this software tool from the Windows Start menu -> SIMATIC -> SIMATIC NET -> Settings.

Removing a CP 5512 from the PC

Before a CP 5512 can be removed from the PC, the following steps must be taken:

1. The CP must first be set to PG operation.
To do this, go to the Station Configuration Editor and deleted the CP 5512 there.

2. Double-click on the "Remove or eject hardware" icon in the taskbar and deactivate the CP 5512.

Error message after restarting the computer in Windows Server 2003

With the Windows Server 2003 operating system, an error message is generated if the CP 5512 communications processor was removed. This error message appears after restarting the computer and indicates that a service could not be started. Please acknowledge this message.

7 CP 5611/CP 5611 MPI Communications Processor

Please read the Installation Instructions supplied in paper form with the CP 5611.

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to Supported Windows Operating Systems"

· Section 25 "Information, Restrictions and Notes Relating to OPC"

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 29 "Notes on C Programming Interfaces"

· Section 30 "Notes on Configuration, Configuring and NCM"

You only need to read the other sections if they relate directly to your product.

7.1 Restrictions

No multiprocessor system

The CP 5611 is not approved for operation in a PC with a multiprocessor system, for example double Pentium.

Operation with a PC with hyperthreading is also not released because it has not been tested.

Restrictions for PCs

If a PC 620 Compact Celeron 300 MHz is operated with two CP 5614 modules, problems arise when using a CP 5611 at a data transmission rate of 12 Mbps. You should avoid using a CP 5611 with two CP 5614 modules in the PC 620.

7.2 Notes on Commissioning

Starting the Plug-and-Play mechanism manually

If the Plug-and-Play mechanism does not find the driver after installing the CP and then rebooting the computer, the computer must be forced to find the driver at the instigation of the user.

Follow the steps below:

1. Restart your computer.

2. Go to the Device Manager (taskbar Start -> Control Panel -> System -> Hardware tab -> Device Manager button).

3. In the "Device Manager" dialog, click the "Scan for hardware changes "button in the menu bar.

4. Confirm all the following dialogs with "Next".

7.3 Notes on Configuration and Configuring

Properties Page in the Station Configuration Editor

In the properties page of the Station Configuration Editor, only fixed PROFIBUS bus profiles can be created for node initialization.

User-specific bus parameters for large network spans and networks such as redundant OLM rings can be specified with the "Configuration Console" tool.

You can start this software tool from the Windows Start menu -> SIMATIC -> SIMATIC NET -> Settings.

8 SOFTNET-S7 (for PROFIBUS)

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to Supported Windows Operating Systems"

· Section 25 "Information, Restrictions and Notes Relating to OPC"

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 29 "Notes on C Programming Interfaces"

· Section 30 "Notes on Configuration, Configuring and NCM"

You only need to read the other sections if they relate directly to your product.

8.1 Version History

Version	Changes/Additionally Supported Functions
V6.2	· Windows 2000 + SP4 is supported. · Windows Server 2003 is supported.
V6.1.1	Windows 2000 is supported on the same CD as Windows XP.
V6.1	Windows XP is supported.
V6.0.5 HF2	· V6.0.5 Hotfix 2 also contains Hotfix 1. · WinCC Version 5.1, along with SIMATIC NET V6.0.5, can only be used with Hotfix 2.
V6.0.5	With STEP 7 or SIMATIC NCM PC the "Send bus parameters" parameter assignment is possible.
V6.0	· Support for Windows 2000 · New, uniform configuration with SIMATIC NCM PC or STEP 7 instead of with lots of tools (COML S7, COM PB) · Windows NT, Windows 2000: bugs fixed in DP C2
V5.1	· Message services extend the SAPI S7 programming interface. These new services are described in the latest issue of the manual S7 Programming Interface. · Return values of the "s7_receive" function: When evaluating the return values of the "s7_receive" function, if unexpected values occur (for example, in the default branch of the corresponding switch statement ), the s7_discard_msg function must be called.
V5.0	· The SAPI S7 programming interface has been extended with new BSEND/BRECEIVE services for the transfer of large data fields blocks of data (up to 64 Kbytes). These new services are described in the latest S7 Programming Interface manual. · The trace concept was modified for the S7 programming interface; when the trace function is activated now, as default the outputs are written to a trace file with a maximum size of 10,000 lines. If this file becomes full, a new file is created. When this is full, the oldest file is overwritten.
V2.2	· Numerous diagnostic functions for device parameter assignments in the PG/PC interface program. · Display of an error text in a message window when there are serious operational problems. · When using the standard and universal bus profiles, the network configuration (number of masters, number of slaves) can be taken into account. · Windows NT: Simplified installation of CardWare (required to operate the CP 5511). · The page for setting SAPs has been omitted. This setting can now be made in the S7 page. · A link to Visual Basic is available.
V2.1	· A data transmission rate of 45.45 Kbps is supported.

8.2 Restrictions

No parallel operation

Operating several SOFTNET CPs in one computer is not supported unless the second CP is used solely for configuration purposes with STEP 7.

The parallel operation of several protocols via SOFTNET CPs is not supported.

Properties Page in the Station Configuration Editor

In the properties page of the Station Configuration Editor, only fixed PROFIBUS bus profiles can be created for node initialization.

User-specific bus parameters for large network spans and networks such as redundant OLM rings can be specified with the "Configuration Console" tool.

You can start this software tool from the Windows Start menu -> SIMATIC -> SIMATIC NET -> Settings.

Versions

If you use the CP 5511 or CP 5611, this CP must have at least hardware version 4.

CP 5411

Use of the CP 5411 is no longer approved.

Error message after restarting the computer in Windows Server 2003

8.3 Notes on Configuration and Configuring

Configuration limits and performance data of the modules

You will find the configuration limits and performance data of the modules on the Siemens Web pages as FAQs under entry ID 15227599.

· German link: http://www4.ad.siemens.de/view/cs/de/15227599

· English link: http://www4.ad.siemens.de/view/cs/en/15227599

The CP 5611 is no longer detected

If a CP 5611 communications processor is no longer detected by the SIMATIC environment after inserting it in a different PCI slot, all the CPs of the type CP 5611 will have to be uninstalled in the Windows Device Manager under SIMATIC NET.

Afterwards start "Find New Hardware" in the Device Manager and follow the instructions of the operating system.

9 SOFTNET-DP (for PROFIBUS)

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to Supported Windows Operating Systems"

· Section 25 "Information, Restrictions and Notes Relating to OPC"

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 29 "Notes on C Programming Interfaces"

· Section 30 "Notes on Configuration, Configuring and NCM"

You only need to read the other sections if they relate directly to your product.

9.1 Version History

Version	Changes/Additionally Supported Functions
V6.2	· Windows 2000 + SP4 is supported. · Windows Server 2003 is supported.
V6.1.1	Windows 2000 is supported on the same CD as Windows XP.
V6.1	Windows XP is supported.
V6.0.5 HF2	· V6.0.5 Hotfix 2 also contains Hotfix 1. · WinCC Version 5.1, along with SIMATIC NET V6.0.5, can only be used with Hotfix 2.
V6.0.5	Bugs fixed
V6.0	· Support for Windows 2000 · Windows NT, Windows 2000: new, uniform configuration with SIMATIC NCM PC or STEP 7 instead of with a lot of tools (COML S7, COM PB) · Windows NT, Windows 2000: bugs fixed in DP C2
V5.3.1	Bugs fixed for operation under Windows NT
V5.1	· The DP master class 1 responds to the master diagnostic request of a DP master class 2. · Master class 2 applications created with Version 5.0 must be recompiled if you want to use them with V5.1. Reason: The User Include File mcl2_usr.h was modified.
V5.0	· It is no longer possible to operate non-standard slaves. · As an alternative to operation as a master class 1, it is also possible to operate as a master class 2 (diagnostic master).
V2.2	· Numerous diagnostic functions for device parameter assignments in the PG/PC interface program. · Display of error texts in a message window when there are serious problems during operation. · Windows NT: Simplified installation of CardWare (required to operate the CP 5511).
V2.1	· A data transmission rate of 45.45 Kbps is supported. · In addition to the standard DP, operation as a DP master class 2 (DPC2) is also supported.

9.2 Restrictions

No parallel operation

Operating several SOFTNET CPs in one computer is not supported unless the second CP is used solely for configuration purposes with STEP 7.

The parallel operation of several protocols via SOFTNET CPs is not supported.

Global control different from the CP 5412 (A2)

The DP interface of the CP differs slightly in the dynamics and functionality from that of the CP 5412 (A2): Cyclic, global control frames that could be configured with COM PROFIBUS for the CP 5412 (A2) are not supported by the CP 5511, CP 5512, and CP 5611).

Terminal Services

Operation of SOFTNET-DP with Terminal Services (Thin Clients) has not been released.

Versions

If you use the CP 5511 or CP 5611, this CP must have at least hardware version 4.

CP 5411

Use of the CP 5411 is no longer approved.

Error message after restarting the computer in Windows Server 2003

9.3 Notes on Configuration and Configuring

Properties Page in the Station Configuration Editor

In the properties page of the Station Configuration Editor, only fixed PROFIBUS bus profiles can be created for node initialization.

User-specific bus parameters for large network spans and networks such as redundant OLM rings can be specified with the "Configuration Console" tool.

You can start this software tool from the Windows Start menu -> SIMATIC -> SIMATIC NET -> Settings.

The CP 5611 is no longer detected

Afterwards start "Find New Hardware" in the Device Manager and follow the instructions of the operating system.

10 SOFTNET-DP Slave (for PROFIBUS)

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to Supported Windows Operating Systems"

· Section 25 "Information, Restrictions and Notes Relating to OPC"

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 29 "Notes on C Programming Interfaces"

· Section 30 "Notes on Configuration, Configuring and NCM"

You only need to read the other sections if they relate directly to your product.

10.1 Version History

Version	Changes/Additionally Supported Functions
V6.2	· Windows 2000 + SP4 is supported. · Windows Server 2003 is supported.
V6.1.1	Windows 2000 is supported on the same CD as Windows XP.
V6.1	Windows XP is supported.
V6.0.5 HF2	· V6.0.5 Hotfix 2 also contains Hotfix 1. · WinCC Version 5.1, along with SIMATIC NET V6.0.5, can only be used with Hotfix 2.
V6.0.5	Bugs fixed
V6.0	· Windows NT, Windows 2000: access point DPSONLINE no longer exists. · Windows NT, Windows 2000: Interface parameter assignments for the CP 5511 (PROFIBUS DP slave) and CP 5611 (PROFIBUS DP slave) no longer exist, instead the slave can be operated via any access point with an interface parameter assignment CP 5511 (PROFIBUS) or CP 5611 (PROFIBUS). · Windows NT, Windows 2000: new, uniform configuration with SIMATIC NCM PC or STEP 7 instead of with a lot of tools (COML S7, COM PB).
V1.0	The PC can be operated as a DP slave with this software package. Functions for setting the input/output data and for starting/stopping the slave are available.

10.2 Restrictions

Multiple CP operation

Operation of several CPs in one computer is not permitted.

Diagnostics

Diagnostics of the hardware cannot be run in programs such as "Set PG/PC Interface" and "Configuration Console" if the CP is active as a DP slave.

Versions

If you use the CP 5511 or CP 5611 as the DP slave, this CP must have at least hardware version 4.

CP 5411

Use of the CP 5411 is no longer approved.

Terminal Services

Operation of SOFTNET-DP Slave with Terminal Services (Thin Clients) has not been released.

10.3 Notes on Configuration and Configuring

Properties Page in the Station Configuration Editor

In the properties page of the Station Configuration Editor, only fixed PROFIBUS bus profiles can be created for node initialization.

User-specific bus parameters for large network spans and networks such as redundant OLM rings can be specified with the "Configuration Console" tool.

You can start this software tool from the Windows Start menu -> SIMATIC -> SIMATIC NET -> Settings.

GSD file

When creating a GSD file for a SOFTNET DP slave, please note the following information in addition to Section 4.2 "Access to the CP 5x11, range of functions of the DP slave, GSD file" in the "DP slave programming interface for CP 5511 and CP 5611" manual. These points also apply to the CP 5512:

· In the configuration data of the submodule definition, only use "bytes" for the length of the data units.

· In the configuration data of the submodule definition, only use "byte consistency" for the consistency.

· Do not enter any empty submodules.

· The maximum data length per submodule is 16 bytes.

· The total length of all inputs or outputs is 122 bytes.

· If you use the GSD file "siem8076.gsd", remember that this is only an example. If you want to create a user program that uses the OPC interface, you must change the Ident number in the GSD file from Ident_Number=0x8076 to 0x9001.

Configuration of the SOFTNET DP slave with the CP 5511, CP 5512 and CP 5611 modules as slave

With SIMATIC NCM PC V5.1 Service Pack 2 or higher or STEP 7 V5.1 Service Pack 4 or higher, there are several ways of configuring a PC (with CP 5511, CP 5512 and CP 5611) as a DP slave. These are described below.

1st option: Configured operation (for example for OPC)

Step	Description
1	With this type of configuration, the CP 5511, CP 5512 and CP 5611 modules must first be set to the configured mode (can be set with the "Configuration Console").
2	In the SIMATIC NCM PC or STEP 7 using the hardware component "PC station as DP slave" in the hardware catalog (hardware catalog -> PROFIBUS DP -> already configured stations -> PC station as DP slave) configure the CP 5511, CP 5512 and CP 5611 modules as a slave, by dragging the entry to the required DP master. This links the slave to the CP and the slave appears as an icon with a green network adapter that must be configured with universal modules.
3	This configuration can be loaded on the PC station.

With this option, the PNO number is fixed: 9001 (hex)

2nd option: Unconfigured operation (for example for old applications based on the C interface)

Step

Description

With this type of configuration, the CP 5511, CP 5512, and CP 5611 modules must be set to the PG mode (in other words, not the configured mode) that can also be set with the "Configuration Console" tool. The slave is assigned a PROFIBUS address with the "Set PG/PC Interface" program. The remaining steps required to configure the slave are part of the user program.

At the master end, you require a separate GSD file describing the slave and the corresponding user program (application). Depending on the configuration you require, modify the supplied sample GSD file "demo.gsd"

(C:\programs\siemens\simatic.net\dp\demo.gsd) with a simple text editor.

(For more detailed information, refer to the "readme.rtf" for the SOFTNET DP slave and the manual describing the DP slave programming interface).

This GSD file is imported into SIMATIC NCM PC or STEP 7 (both V5.1 with Service Pack 4 or higher). Following this, the DP slave described by the GSD file is available in the hardware catalog of SIMATIC NCM PC or STEP 7 under (hardware catalog -> PROFIBUS DP -> Additional Field Devices -> General) and can be included in the configuration by dragging with the mouse.

For more detailed information, refer to the manual on the DP slave programming interface.

Active / passive slave

The CP 5511, CP 5512 and CP 5611 modules can be operated as active slaves (a special form of slave that is also master at the same time) or as passive slaves.

In the unconfigured mode, the slave is always an active slave. In the configured mode, you can decide whether the slave is an active or passive slave in SIMATIC NCM PC or STEP 7.

Note the following: The configuration cannot be downloaded to a passive slave from a remote station.

The data transmission rate and the station address are only adopted from the C interface for a passive slave.

With an active slave, the values are set in the configuration or in "Set PG/PC Interface" since they are common to the master and slave.

The CP 5611 is no longer detected

Afterwards start "Find New Hardware" in the Device Manager and follow the instructions of the operating system.

11 CP 1613 Communications Processor

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to Supported Windows Operating Systems"

· Section 25 "Information, Restrictions and Notes Relating to OPC"

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 29 "Notes on C Programming Interfaces"

· Section 30 "Notes on Configuration, Configuring and NCM"

You only need to read the other sections if they relate directly to your product.

11.1 Restrictions

Not with SOFTNET IE

It is not possible to operate SOFTNET IE over the CP 1613.

Reset

Restarting or resetting a module is only possible when PC network operation is deactivated.

AUI cable

The CP 1613 has two connectors for connecting network cables:

· 15-pin D-sub female connector with slide lock mechanism for connecting either an AUI transceiver cable (AUI – Attachment Unit Interface) or an ITP cable
(ITP – Industrial Twisted Pair)

· RJ-45 jack for connecting a TP cable (TP – Twisted Pair)

If the AUI interface is used for the AUI transceiver cable, breaks of 2 to 3 seconds can occur sporadically in communication. The monitoring time for timeouts must not, therefore, be set to less than 5 seconds!

IP addresses

The IP address for the automation protocols via ISO-on-TCP (synonymous with TCP/IP (RFC 1006)) must be different from the NDIS IP address for communication over PC networks.

11.2 Notes on Commissioning

Plug-and-Play mechanism does not find the driver

If the Plug-and-Play mechanism does not find the driver after installing the CP and then rebooting the computer, the computer must be forced to find the driver at the instigation of the user.

Follow the steps below:

1. Restart your computer.

2. Go to the Device Manager (taskbar Start -> Control Panel -> System -> Hardware tab -> Device Manager button).

3. In the "Device Manager" dialog, click the "Scan for hardware changes "button in the menu bar.

4. Confirm all the following dialogs with "Next".

Two TCP/IP addresses

On the CP 1613, you can set two IP addresses during configuration; the reason for this is as follows:

On the one hand, the CP 1613 communications processor is intended for operation with office communications protocols, for example TCP/IP. For this, the CP 1613-NDIS adapter must be installed and individual office communications protocols assigned to it. The office communications protocols run on the PC.

On the other hand, the CP 1613 can also be used for automation purposes with the SIEMENS industrial protocols, for example SEND/RECEIVE, SAPI-S7, STEP 7, and TF. The protocols can either be handled over the transport protocol ISO or TCP/IP. Both transport protocols run in the firmware of the CP 1613. The interfacing of the TCP/IP transport protocol to the SIEMENS industrial protocols is according to the RFC 1006 specification. On the CP 1613, a total of two TCP/IP transport protocol functions can be operated at the same time:

· Office communications interfacing

· Interfacing SIEMENS industrial protocols

Both interfaces must be assigned different TCP/IP addresses to identify them uniquely.

Several CP 1613 modules

If several CP 1613 modules are installed, the CP 1613 NDIS adapter driver must be installed for all modules. If you make any changes to the configuration of the CP 1613 NDIS adapter (activate, deactivate etc.), you should always check the NDIS IP addresses afterwards.

MAC addresses

After installing a new CP 1613 module, you should always compare its active MAC address with the MAC addresses of other CP 1613 modules or other Ethernet modules. Make sure that all the Ethernet modules operated in a network have different MAC addresses.

If the CP 1613 installed in the computer is replaced by another CP 1613 in the same slot, the new CP 1613 will be assigned the MAC address of the CP 1613 that was removed from the computer.

Remedy
Follow the steps below:

1. Select the relevant module and uninstall it.

2. Then restart your computer.

Installing a CP 1613 after installing the SIMATIC NET CD under Windows XP/Windows Server 2003

If a CP 1613 is installed in the computer after you have installed the SIMATIC NET Software, the "Siemens CP 1613 Ethernet PCI Adapter" is not installed automatically after you restart the PC. Instead, the Hardware Manager opens. Use this to install the "Siemens CP 1613 Ethernet PCI Adapter" (click the "Next" and "Finish" buttons).

Removal

After removing a CP 1613 module, all the CP 1613 modules remaining in the computer will be taken out of configured operation. This avoids assignment problems.

Time-of-day frames

When configuring the time intervals with STEP 7, only intervals of 1 s or 10 s are possible.

CP 1613 is displayed in the Device Manager as "Ethernet Controller"

Select the relevant module and uninstall it. Then restart your computer.

11.3 Notes on Configuration and Configuring

Configuration limits and performance data of the modules

You will find the configuration limits and performance data of the modules on the Siemens Web pages as FAQs under entry ID 15227599.

· German link: http://www4.ad.siemens.de/view/cs/de/15227599

· English link: http://www4.ad.siemens.de/view/cs/en/15227599

11.4 CP 1613 SNMP agent

Description

As of product version V6.0.5, the CP 1613 includes the CP 1613 SNMP agent (Simple Network Management Protocol agent in its firmware). This agent replies to the requests of an SNMP management system (SNMP manager), for example the SNMP OPC server. Installation is not necessary. This is always active.

The CP 1613 SNMP agent supports SNMPv1 (SNMP Version 1.0) and RFC 1213 MIBII objects (MIB — Managed Information Base).

For more detailed information on the SIMATIC NET SNMP service, refer to the HTML document "Industrial Communication for PG/PC".

Addressing

The CP 1613 SNMP agent can be accessed using the IP address of the CP 1613 (IP address for the automation protocols over ISO-on-TCP (synonymous with TCP/IP (RFC 1006))).

In contrast, the Windows SNMP agent is accessible via the NDIS-IP address (IP address for communication over PC networks, if this is configured). For more detailed information on the Windows SNMP service, refer to the Windows help.

Configuration

It is not necessary to configure the CP 1613 SNMP agent. The user can, however, set the "sysLocation", "sysContact" and "sysName" objects. This is done via the network using the SNMP management system. This data is stored on the CP 1613. If you replace the CP 1613, these objects must therefore be set again.

Safety

For safety reasons, only the "sysLocation", "sysContact" and "sysName" objects can be set. All other objects can only be read.

The integration of the SNMP agent in the firmware provides additional security. Access to the data of the computer over SNMP is therefore impossible.

For more detailed information on security, refer to the HTML document "Industrial Communication for PG/PC".

Restrictions

Only the "public", (read only) and "private" (read and write) communities are supported. Reconfiguring or adding communities is not possible. Traps are not sent by the CP 1613 SNMP agent.

12 S7-1613

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to Supported Windows Operating Systems"

· Section 25 "Information, Restrictions and Notes Relating to OPC"

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 29 "Notes on C Programming Interfaces"

· Section 30 "Notes on Configuration, Configuring and NCM"

You only need to read the other sections if they relate directly to your product.

12.1 Version History

Version	Changes/Additionally Supported Functions
V6.2	· Windows 2000 + SP4 is supported. · Windows Server 2003 is supported. · Bugs fixed
V6.1.1	Windows 2000 is supported on the same CD as Windows XP.
V6.1	Windows XP is supported.
V6.0.5 HF2	· V6.0.5 Hotfix 2 also contains Hotfix 1. · WinCC Version 5.1, along with SIMATIC NET V6.0.5, can only be used with Hotfix 2.
V6.0.5	· CP 1613 SNMP Agent (SNMPv1, MIBII objects, RFC 1213) · Bugs fixed · Improved compatibility with Industrial Ethernet OMC · Promiscuous mode for NDIS 1613 · If network parameters are fixed, the autonegotiation mode is deactivated. · Configured routing functionality
V6.0	· New, uniform configuration with SIMATIC NCM PC or STEP 7 instead of with lots of tools (COML S7, COM PB) · PG routing functionality · Support of the SEND-RECEIVE job AWAIT_CONN_REQ_USER for ISO-on-TCP (synonymous with TCP/IP (RFC 1006)) and ISO · Improved compatibility with the optical media converter OMC TP11
V2.1 SP2	· Bugs fixed · The following new services are supported over the SEND/RECEIVE interface with ISO: a.) Sending and receiving datagrams and b.) Setting and clearing multicast addresses
V2.1 SP1	Bugs fixed
V2.1	· Windows 2000 Professional is supported. · Bugs fixed · Improved performance
V2.0	· ISO-on-TCP (synonymous with TCP/IP (RFC 1006)) is supported · Transfer parameters set using the "Set PG/PC Interface" program.
V1.1	Base version

12.2 Restrictions and Information on All Software Products for the CP 1613

PC Network operation

PC network operation is released only for the TCP/IP protocol.

Number does not match slot

If there is more than one CP 1613 module plugged in, the number of the module assigned by the SIMATIC NET software provides no information about the physical slot.

Displayed network parameters

In the "Configuration Console" program, the current network parameters are displayed for the CP 1613 in the "Network Parameters" tab.As long as no valid link to the partner is detected, "unknown" is displayed here.

Since there is no link detection with AUI, the reception of frames is used as a substitute for link detection. If no frames are received when the AUI cable is plugged in, it is assumed that no link exists. A valid link is assumed only when the first frame is received via AUI and the network parameters are output (AUI, 10 Mbps, half duplex).

Note on the SEND/RECEIVE programming interface and OPC

Using "Expedited Data" over ISO connections:

If data packets of the "Expedited Data" type are transferred on a SEND/RECEIVE ISO connection, the receiving application at the PC must make sure that this data is actually accepted. Otherwise, the buffering of these data packets can lead to a lack of memory that can eventually cause the connection to be terminated.

This means that if you use an ISO connection with your OPC user program, a receive item must be activated on this connection.

12.3 Further restrictions

Connection monitoring with ISO-on-TCP (synonymous with TCP/IP (RFC 1006))

If an application does not provide reception resources, the detection of the disconnect caused by the partner can take several minutes. Connection establishment between two PCs with a CP 1613 can take several minutes if more than 32 connections need to be established.

PC-PC communication with CP 1613 to SOFTNET-S7 with Fast Acknowledge

Communication between a PC with a CP 1613 communications processor and another PC with SOFTNET-S7 over ISO-on-TCP (synonymous with TCP/IP (RFC 1006)) is not possible under the following conditions:

· PC with CP 1613 only sends.

· PC with CP 1613 does not provide receive resources.

· Fast Acknowledge is activated ("Configuration Console").

Remedy: Deactivate Fast Acknowledge.

Segment sizes for SEND/RECEIVE

With SEND/RECEIVE, messages with the PLC blocks FC5, FC6 are supported up to a maximum of 4 Kbytes of user data; with the PLC blocks FC50 and FC60 up to a maximum of 8 Kbytes.

12.4 Notes on Configuration and Configuring

Configuration limits and performance data of the modules

You will find the configuration limits and performance data of the modules on the Siemens Web pages as FAQs under entry ID 15227599.

· German link: http://www4.ad.siemens.de/view/cs/de/15227599

· English link: http://www4.ad.siemens.de/view/cs/en/15227599

13 PG-1613

Please read the Installation Instructions supplied in paper form with the CP 1613.

Please refer to the information in Section 12, "Restrictions and Information for all Software Products of the CP 1613" for all software products relating to the CP 1613.

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to Supported Windows Operating Systems"

· Section 25 "Information, Restrictions and Notes Relating to OPC"

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 30 "Notes on Configuration, Configuring and NCM"

· Section 33 "Routing"

You only need to read the other sections if they relate directly to your product.

The PG-1613 product is available only for Windows 2000.

13.1 Version History

Version	Changes/Additionally Supported Functions
V6.2	· Windows 2000 + SP4 is supported. · Bugs fixed
V6.1.1	Windows 2000 is supported on the same CD as Windows XP.
V6.0.5 HF2	· V6.0.5 Hotfix 2 also contains Hotfix 1. · WinCC Version 5.1, along with SIMATIC NET V6.0.5, can only be used with Hotfix 2.
V6.0.5	· CP 1613 SNMP Agent (SNMPv1, MIBII objects, RFC 1213) · Bugs fixed · Improved compatibility with Industrial Ethernet OMC · Promiscuous mode for NDIS 1613 · If network parameters are fixed, the autonegotiation mode is deactivated.
V6.0	· New, uniform configuration with SIMATIC NCM PC or STEP 7 instead of with lots of tools (COML S7, COM PB). · PG routing functionality · Support of the SEND/RECEIVE job AWAIT_CONN_REQ_USER for ISO-on-TCP (synonymous with TCP/IP (RFC 1006)) and ISO · Improved compatibility with the optical media converter OMC TP11
V2.1 SP2	· Bugs fixed · The following new services are supported over the SEND/RECEIVE interface with ISO: a.) Sending and receiving datagrams and b.) Setting and clearing multicast addresses
V2.1 SP1	Bugs fixed
V2.1	· Windows 2000 Professional is supported · Bugs fixed · Improved performance
V2.0	· ISO-on-TCP (synonymous with TCP/IP (RFC 1006)) is supported · Transfer parameters set using the "Set PG/PC Interface" program.
V1.1	Base version

13.2 Restrictions

Late disconnect with ISO-on-TCP (synonymous with TCP/IP (RFC 1006))

If an application does not provide reception resources, the detection of the disconnect caused by the partner can take several minutes.

13.3 Notes on Configuration and Configuring

Configuration limits and performance data of the modules

You will find the configuration limits and performance data of the modules on the Siemens Web pages as FAQs under entry ID 15227599.

· German link: http://www4.ad.siemens.de/view/cs/de/15227599

· English link: http://www4.ad.siemens.de/view/cs/en/15227599

14 TF-1613

Please refer to the information in Section 12, "Restrictions and Information for all Software Products of the CP 1613" for all software products relating to the CP 1613.

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to Supported Windows Operating Systems"

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 29 "Notes on C Programming Interfaces"

You only need to read the other sections if they relate directly to your product.

The TF-1613 product is available only for Windows 2000.

14.1 Version History

Version	Changes/Additionally Supported Functions
V6.2	· Windows 2000 + SP4 is supported. · Bugs fixed
V6.1.1	Windows 2000 is supported on the same CD as Windows XP.
V6.0.5 HF2	· V6.0.5 Hotfix 2 also contains Hotfix 1. · WinCC Version 5.1, along with SIMATIC NET V6.0.5, can only be used with Hotfix 2.
V6.0.5 HF1	Hotfix 1 contains bug fixes for variables of the data type S5REAL in the SEND/RECEIVE protocol of the SIMATIC NET OPC server.
V6.0.5	· CP 1613 SNMP Agent (SNMPv1, MIBII objects, RFC 1213) · Bugs fixed · Improved compatibility with Industrial Ethernet OMC · Promiscuous mode for NDIS 1613 · If network parameters are fixed, the autonegotiation mode is deactivated.
V2.1 SP2	Bugs fixed
V2.1 SP1	Bugs fixed
V2.1	· Windows 2000 Professional is supported · Bugs fixed
V2.0	No essential changes
V1.1	Base version

14.2 Restrictions

PDU Size

The "PDU size" parameter of an "application relation" must not exceed the value 4000! This is set when you create a database with the "COML TF" program.

"tf_astate_path" job

Only one asynchronous job of the type tf_astate_path may be active at any one time per application relation.

Windows Terminal Server

The TF-1613 product is not released for operation with Windows Terminal Server.

Simultaneous use of the TF Protocol with other protocols

Simultaneous operation of the TF protocol and other protocols is not permitted on one CP 1613 communications processor.

Multiple processor mode

The multiple processor mode has not been released.

14.3 Notes on Configuration and Configuring

TF communication over the ISO transport protocol

TF communication is possible only over the ISO transport protocol.

Adaptation of the stf_conf.dat file

Please change the following line in the stf_conf.dat file:

SCP_device = /CP_H1_1:/SCP /* SCP device path name */

to:

SCP_device = /CP_H1_1:/AP /* SCP device path name */

The stf_conf.dat file must be copied to the working folder of the TF application!

COML TF

In the "COML TF" program, the standard CP type "CP 1413 TF" is compatible with the CP type "CP 1613 TF".

Configuration example

An example of TF configuration is described in the following files (after you have installed the service pack):

· "Readme.txt" in the "simatic net\tf1613\tf\sample" folder describes the example.

· "h1tfcl1.txt", "h1tfsv11.txt" and "h1tfsv12.txt" contain the sample configuration files in the "simatic net\tf1613\tf\sample\db" folder.

· "h1.txt" in the "simatic net\comh1tf" folder describes the structure of the TF configuration files.

Configuration limits and performance data of the modules

You will find the configuration limits and performance data of the modules on the Siemens Web pages as FAQs under entry ID 15227599.

· German link: http://www4.ad.siemens.de/view/cs/de/15227599

· English link: http://www4.ad.siemens.de/view/cs/en/15227599

Parallel synchronous TF jobs in different threads

The use of parallel synchronous TF jobs in different threads of an application is not permitted.

15 S7-REDCONNECT and S7-REDCONNECT Upgrade

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to Supported Windows Operating Systems"

· Section 25 "Information, Restrictions and Notes Relating to OPC"

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 29 "Notes on C Programming Interfaces"

· Section 30 "Notes on Configuration, Configuring and NCM"

You only need to read the other sections if they relate directly to your product.

Please note the descriptions of fault tolerant systems in the "Industrial communication with PG/PC" manual.

15.1 Version History

Version	Changes/Additionally Supported Functions
V6.2	· Windows 2000 + SP4 is supported. · Windows Server 2003 is supported. · Bugs fixed
V6.1.1	Windows 2000 is supported on the same CD as Windows XP.
V6.1	Windows XP is supported.
V6.0.5 HF2	· V6.0.5 Hotfix 2 also contains Hotfix 1. · WinCC Version 5.1, along with SIMATIC NET V6.0.5, can only be used with Hotfix 2.
V6.0.5	· CP 1613 SNMP Agent (SNMPv1, MIBII objects, RFC 1213) · Bugs fixed · Improved compatibility with Industrial Ethernet OMC · Promiscuous mode for NDIS 1613 · If network parameters are fixed, the autonegotiation mode is deactivated.
V6.0	· Includes "Advanced PC Configuration" (APC) · Supports only CP 1613
V1.4	This version supports only the CP 1613 module. For the first time, the functions for 4-path operation and maximum CP redundancy are supported.
V1.3.1	· This version is a bug-fix version of Version 1.0 or 1.1 and supports the CP 1613, CP 1413, CP 5412 (A2) modules for all network types. · Operation with an upgrade license is possible as of this version.
V1.2.3	This version is a bug-fix version of Version 1.0 and supports the CP 1413 and CP 5412 (A2) modules for all network types. This is supplied only along with PCS 7 V5.0.
V1.1	This version supports the CP 1613 module for the first time in the following configuration: 1 CP 1613 module, Industrial Ethernet optical networks.
V1.0	Base version The SAPI S7 programming interface has been extended with new BSEND/BRECEIVE services for the transfer of large data fields blocks of data (up to 64 Kbytes). These new services are described in the latest S7 Programming Interface manual. The trace concept was modified for the S7 programming interface; when the trace function is activated now, as default the outputs are written to a trace file with a maximum size of 10,000 lines. If this file becomes full, a new file is created. When this is full, the oldest file is overwritten.

15.2 Notes on the Product

Use of the "Upgrade S7-REDCONNECT" product

The "Upgrade S7-REDCONNECT" product is intended for users who have already installed the "S7‑1613" product (possible only as of V2.1 under Windows 2000) and now want to use the functions of "S7‑REDCONNECT".

Licenses required for "S7-REDCONNECT"

To operate "S7-REDCONNECT", you require one authorization key (license).

Licenses required for "Upgrade S7-REDCONNECT"

To operate "Upgrade S7-REDCONNECT" you require two authorization keys (2 two licenses from two key diskettes):

· Authorization for the "Upgrade S7-REDCONNECT" product

· Authorization for the "S7-1613" product (only possible as of V2.1 under Windows 2000)

15.3 Restrictions

Do not use AUI cable

The CP 1613 has two jacks for connecting network cables: The 15-pin sub‑D female connector with slide locking mechanism both for connection of an AUI transceiver cable (AUI ‑ Attachment Unit Interface) and for connection of an ITP cable (ITP – Industrial Twisted Pair), and the RJ-45 jack for connecting a TP cable (TP – Twisted Pair).

For fault-tolerant connections, use only the 15-pin D-sub female connector for ITP cable or the RJ-45 jack for TP cable but not the AUI port for AUI transceiver cables!

Not between PCs

Redundant S7 connections between PCs are not possible.

No fault-tolerance for SEND/RECEIVE

The "S7-REDCONNECT" and "Upgrade S7-REDCONNECT" products support fault-tolerance for S7 communication only and not for SEND/RECEIVE communication

Pause if the reserve CPU fails

If the reserve CPU of an H system fails, a pause of several seconds can occur in the communication to the master.

15.4 Notes on Configuration and Configuring

Required configuration software

To configure connections, you require the following software packages:

· STEP 7 V5.0 or higher for 2-path communication.

· STEP 7 V5.1 service pack 4 or higher for 4-path communication.

· SIMATIC S7 H systems optional package

Fixed parameter values

The settings of persistence count and abort timeout using the SAPI S7 mini DB have no effect on fault-tolerant S7 connections. On such connections, fixed internal values are used to achieve the necessary, short failover times.

How to configure fault tolerance

Step	Description
1	Enter all the hardware components of your automation system in STEP 7, HW Config. These include both the CPs in the SIMATIC S7 stations as well as the user applications on the PCs and the SIMATIC NET network adapters.
2	Following this, you can configure the fault tolerant S7 connections for the individual user programs: · After saving in HW Config, you set the addresses for the CPs with STEP 7, NetPro and connect the CPs to the appropriate subnets. · Select "S7 connection fault-tolerant" for the connection type parameter. · In the properties dialog, you decide whether you want to 2 or 4 path redundancy for this connection by activating the "max. CP redundancy" check box.
3	Save and compile in NetPro to generate the databases (SDB and XDB files). Download the databases to the S7 stations and download or import them to the configure PC stations.

Please remember that following any change in the connection configuration in STEP 7, NetPro the current configuration must be downloaded or imported again into the S7 and PC stations.

Configuring a CP 443-1

If you insert a CP 443-1 into a SIMATIC S7 station, the "Activate fast failover of the connection" check box must be activated (dialog box "Properties – CP 443-1 ..." ‑> Options -> Ethernet Profile for Fault-Tolerant Connections -> activate fast failover of the connection).

Do Not Activate a TF Database

When working with fault-tolerant connections, no (!) database (LDB file) must be activated in the "Set PG/PC Interface" under "Interface parameter assignment used" -> Properties -> TF Protocol.

The use of LDB files for connection configuration is intended to allow compatibility with older products under the Windows 2000 operating system and has not been released for operating fault-tolerant connections on the same CP.

How 4-path redundancy functions

If you have configured your fault-tolerant S7 connection with maximum CP redundancy (4 paths), if the productive or reserve path fails, another connection path will be established (assuming it is available). The failover can take between several seconds and several minutes depending on your configuration.

The connection is then redundant again (over a new path).

Please note that depending on the configuration, it is possible that the two connection paths now include non-redundant components (not ideal redundancy). At this point, one further redundant component can fail without S7 communication being disturbed (as long as it is not used by both paths).

For more detailed information, refer to the HTML document "Industrial Communication for PG/PC".

Configuration limits and performance data of the modules

You will find the configuration limits and performance data of the modules on the Siemens Web pages as FAQs under entry ID 15227599.

· German link: http://www4.ad.siemens.de/view/cs/de/15227599

· English link: http://www4.ad.siemens.de/view/cs/en/15227599

15.5 "S7 Connection Diagnostics"

Area of application

This program makes it easier to commission fault-tolerant connections and informs you when there is a problem on a specific connection path.

Start

The use of the diagnostic program is possible only when you have downloaded a STEP 7 configuration.

You start the diagnostic program from the SIMATIC path (taskbar Start -> SIMATIC -> SIMATIC NET -> Industrial Ethernet -> S7RedConnect -> S7 Connection Diagnostic).

Online help

Click on ? -> Contents for information on the program.

Dealing with memory access violations

If there is a memory access violation in an application that works with S7-REDCONNECT, or if it no longer reacts for one reason or another, it is possible that the display in the diagnostic program is no longer refreshed.

In this case, close all applications that use S7 connections and restart them.

Software diagnostic interface

It is also possible to read diagnostic data from your own application program. See Section "Diagnostic Services for Fault-tolerant Connections" in the "S7 Programming Interface" manual.

16 CP 1512 Communications Processor

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to Supported Windows Operating Systems"

· Section 25 "Information, Restrictions and Notes Relating to OPC"

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 29 "Notes on C Programming Interfaces"

· Section 30 "Notes on Configuration, Configuring and NCM"

You only need to read the other sections if they relate directly to your product.

16.1 Note

Current driver diskette (exclusive PC network operation)

Compare the version of this SIMATIC NET CP 1512 software product with the version of your driver diskette.

If the version of the SIMATIC NET CP 1512 software product is newer than that of your driver diskette,

create a new driver diskette by copying the content of the folder (…\SW\cp1512_cp1612\cp1512) to an empty diskette and then use this as the driver diskette.

16.2 Restrictions

Number of modules

Only one (1) module may be inserted per computer.

17 CP 1612 Communications Processor

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to Supported Windows Operating Systems"

· Section 25 "Information, Restrictions and Notes Relating to OPC"

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 29 "Notes on C Programming Interfaces"

· Section 30 "Notes on Configuration, Configuring and NCM"

You only need to read the other sections if they relate directly to your product.

17.1 Note

Current driver diskette (exclusive PC network operation)

Compare the version of this SIMATIC NET CP 1612 software product with the version of your driver diskette.

If the version of the SIMATIC NET CP 1612 software product is newer than that of your driver diskette,

create a new driver diskette by copying the content of the folder (…\SW\cp1512_cp1612\cp1612) to an empty diskette and then use this as the driver diskette.

17.2 Restrictions

Modules per computer

Per computer, only one (1) module can be used in configured mode.

18 SOFTNET-S7 for Industrial Ethernet

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to Supported Windows Operating Systems"

· Section 25 "Information, Restrictions and Notes Relating to OPC"

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 29 "Notes on C Programming Interfaces"

· Section 30 "Notes on Configuration, Configuring and NCM"

You only need to read the other sections if they relate directly to your product.

18.1 Version History

Version	Changes/Additionally Supported Functions
V6.2	· Windows 2000 + SP4 is supported. · Windows Server 2003 is supported. · Bugs fixed
V6.1.1	Windows 2000 is supported on the same CD as Windows XP.
V6.1	Windows XP is supported.
V6.0.5 HF2	· V6.0.5 Hotfix 2 also contains Hotfix 1. · WinCC Version 5.1, along with SIMATIC NET V6.0.5, can only be used with Hotfix 2.
V6.0.5	· Bugs fixed · Configured inter-subnet connections · Configured routing functionality
V6.0	· Windows NT, Windows 2000: new, uniform configuration with SIMATIC NCM PC or STEP 7 instead of with a lot of tools (COML S7, COM PB) · 64 instead of previously 8 connections · PG routing functionality · Support of the SEND-RECEIVE job AWAIT_CONN_REQ_USER for ISO-on-TCP (synonymous with TCP/IP (RFC 1006)) and ISO
V3.3	· Access using dial-up connections is possible. · Under Windows NT 4.0, access using RAS is possible. · Windows 2000 is supported.
V3.0	· TSAP routing functionality · The SAPI S7 programming interface has been extended with new BSEND/BRECEIVE services for the transfer of large data fields blocks of data. These new services are described in the S7 Programming Interface manual. · The trace concept was modified for the SAPI S7 programming interface; when the trace function is activated now, as default the outputs are written to a trace file with a maximum size of 10,000 lines. If this file becomes full, a new file is created. When this is full, the oldest file is overwritten.
V2.0	· Starting several SEND/RECEIVE applications is possible. · ISO-on-TCP (synonymous with TCP/IP (RFC 1006)) can now be called as a Windows NT service.

18.2 Restrictions

Number of network adapters

A maximum of 1 (one) network adapter with SOFTNET-S7 can be operated.

Passive connection establishment with the ISO-on-TCP protocol (synonymous with TCP/IP (RFC 1006))

Passive connection establishment with the ISO-on-TCP protocol (synonymous with TCP/IP (RFC 1006)) is not possible with SOFTNET-S7 for Industrial Ethernet.

Reason: When using the ISO-on-TCP protocol (synonymous with TCP/IP (RFC 1006)), only one user program can use passive connection endpoints. When the Station Configuration Editor is online, it services the only passive connection endpoint. This connection endpoint is therefore blocked for other user programs.

Note on the SEND/RECEIVE programming interface and OPC, use of expedited data over ISO connections

This means that if you use an ISO connection with your OPC user program, a receive item must be activated on this connection.

Instructions relating to older modules

Information on the CP 1401, CP 1411 and CP 1511 modules in other documents can be ignored since these modules have been discontinued.

Gigabit Ethernet

Operation of SOFTNET Industrial Ethernet on network adapters with 1 Gbps has not been released.

Link Aggregation, Trunking

The combination of several network adapters to form one "virtual" network adapter is not supported (in compliance with IEEE 802.3ad standard).

Number of jobs per connection with Industrial Ethernet and S7 protocol

The send credit (number of outstanding jobs per connection) negotiated by the server and client must not be used to the full. At any time, the number of pending jobs per connection must not exceed 1.
Directly after active establishment of the connection, you can check the send credit using the following function:

s7_mini_db_get(S7_MINI_DB_INIT_CNF_AMQ_CALLING)

Segment sizes for SEND/RECEIVE

With SEND/RECEIVE, messages with the PLC blocks FC5, FC6 are supported up to a maximum of 4 Kbytes of user data; with the PLC blocks FC50 and FC60 up to a maximum of 8 Kbytes.

18.3 Notes on Configuration and Configuring

Communication using the Remote Access Service (RAS)

A connection to a partner is established with the integrated "RAS" service. The partner only needs to support the establishment of a TCP/IP connection.

If you want to communicate using RAS, your PC must have an ISDN access (for example, ISDN access over ISDN card or router). The TCP/IP protocol must also be installed.

When the ISDN connection is established, the access point of the application is assigned an IP address set during connection establishment or an IP address from the partner. Set the "access point of the application" for RAS operation in the "Configuration Console" program (Windows taskbar Start -> Simatic -> SIMATIC NET -> Settings -> Configuration Console) as follows:

S7ONLINE (STEP 7) -> TCP/IP -> NdisWanIp

Special parameter setting

If you want to operate a configured ISO transport connection between a PG/PC and a SIMATIC programmable controller, please use the parameter settings shown below on the SIMATIC programmable controller.

Parameter	Value
Retransmission Time for data transfer	2000 ms or higher
Retransmission max. count for data transfer	10 or higher

Lower values, for example the default values, can cause the connection to break down.

Out-of-date STEP 7 hardware catalog

SOFTNET-S7 supports connections as of V6.0 64.

STEP 7 to V5.1 SP2 does not display this in the hardware catalog.

Multiple protocol mode

Multiple protocol mode means that you can communicate with the S7 protocol and the SEND/RECEIVE protocol at the same time. With each of these protocols, you can decide whether or not you want to use the ISO or ISO-on-TCP (synonymous with TCP/IP (RFC 1006)) transport protocol.

Message "MAC address does not exist in Configuration Console"

If you receive the message that the MAC address does not exist in the "Configuration Console" program, you have probably accidentally deleted the "SIMATIC Industrial Ethernet (ISO)" protocol. Reinstall the protocol.

Network bridge

With a network card that has been added to a "Network bridge" added, it is not possible to operate SOFTNET Industrial Ethernet.

If you want to use a network card inserted in a network bridge for SIMATIC NET products, you must first remove it from the network bridge before installing the SIMATIC NET software product CD.

Deactivated network adapters

When you install the SIMATIC PC software over older versions, deactivated network adapters are reactivated.

Configuration limits and performance data of the modules

You will find the configuration limits and performance data of the modules on the Siemens Web pages as FAQs under entry ID 15227599.

· German link: http://www4.ad.siemens.de/view/cs/de/15227599

· English link: http://www4.ad.siemens.de/view/cs/en/15227599

19 SOFTNET-S7 Lean for Industrial Ethernet

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to Supported Windows Operating Systems"

· Section 25 "Information, Restrictions and Notes Relating to OPC"

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 29 "Notes on C Programming Interfaces"

· Section 30 "Notes on Configuration, Configuring and NCM"

You only need to read the other sections if they relate directly to your product.

19.1 Version History

Version

Changes/Additionally Supported Functions

V6.2

· Windows 2000 + SP4 is supported.

· Windows Server 2003 is supported.

· Bugs fixed

V6.1.1

· Windows 2000 is supported on the same CD as Windows XP.

· Base version

19.2 Restrictions

Number of network adapters

A maximum of 1 (one) network adapter with SOFTNET-S7 Lean can be operated.

Number of jobs per connection with Industrial Ethernet and S7 protocol

The send credit (number of outstanding jobs per connection) negotiated by the server and client must not be used to the full. At any time, the number of pending jobs per connection must not exceed 1.

Directly after active establishment of the connection, you can check the send credit using the following function:

s7_mini_db_get(S7_MINI_DB_INIT_CNF_AMQ_CALLING)

Passive connection establishment with the ISO-on-TCP protocol (synonymous with TCP/IP (RFC 1006))

Passive connection establishment with the ISO-on-TCP protocol (synonymous with TCP/IP (RFC 1006)) is not possible with SOFTNET-S7 Lean for Industrial Ethernet. (Reason: When using the ISO-on-TCP protocol (synonymous with TCP/IP (RFC 1006)), only one user program can use passive connection endpoints. When the Station Configuration Editor is online, it services the only passive connection endpoint. This connection endpoint is therefore blocked for other user programs.)

Note on the SEND/RECEIVE programming interface and OPC, use of expedited data over ISO connections

This means that if you use an ISO connection with your OPC user program, a receive item must be activated on this connection.

Instructions relating to older modules

Information on the CP 1401, CP 1411 and CP 1511 modules in other documents can be ignored since these modules have been discontinued.

Gigabit Ethernet

Operation of SOFTNET Industrial Ethernet on network adapters with 1 Gbps has not been released.

Link Aggregation, Trunking

The combination of several network adapters to form one "virtual" network adapter is not supported (in compliance with IEEE 802.3ad standard).

Segment size 4 Kbytes with SEND/RECEIVE

With SEND/RECEIVE, messages with a maximum of 4096 bytes of user data are supported.

Keep in mind the PLC functions FC5, FC6, FC50 and FC60.

19.3 Notes on Configuration and Configuring

Communication using the Remote Access Service (RAS)

A connection to a partner is established with the integrated "RAS" service. The partner only needs to support the establishment of a TCP/IP connection.

If you want to communicate using RAS, your PC must have an ISDN access (for example, ISDN access over ISDN card or router). The TCP/IP protocol must also be installed.

When the ISDN connection is being established, the "access point of the application" is assigned the IP address set during connection establishment or an IP address from the partner. Set the access point of the application for RAS operation as follows in the "Configuration Console" dialog box (taskbar Start -> Simatic -> SIMATIC NET -> Settings -> Configuration Console):

S7ONLINE (STEP 7) -> TCP/IP -> NdisWanIp

Special parameter setting

Parameter	Value
Retransmission Time for data transfer	2000 ms or higher
Retransmission max. count for data transfer	10 or higher

Lower values, for example the default values, can cause the connection to break down.

Multiple protocol mode

Message MAC address does not exist in Configuration Console

Network bridge

With a network card that has been added to a "Network bridge" added, it is not possible to operate SOFTNET Industrial Ethernet.

If you want to use a network card inserted in a network bridge for SIMATIC NET products, you must first remove it from the network bridge before installing the SIMATIC NET software product CD.

Deactivated network adapters

When you install the SIMATIC PC software over older versions, deactivated network adapters are reactivated.

Configuration limits and performance data of the modules

You will find the configuration limits and performance data of the modules on the Siemens Web pages as FAQs under entry ID 15227599.

· German link: http://www4.ad.siemens.de/view/cs/de/15227599

· English link: http://www4.ad.siemens.de/view/cs/en/15227599

20 SOFTNET-PG for Industrial Ethernet

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to Supported Windows Operating Systems"

· Section 25 "Information, Restrictions and Notes Relating to OPC"

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 30 "Notes on Configuration, Configuring and NCM"

You only need to read the other sections if they relate directly to your product.

If you install the SIMATIC NET PC software products under Windows Server 2003, certification messages are displayed. Please confirm the messages. Otherwise the installation will be canceled.

20.1 Version History

Version	Changes/Additionally Supported Functions
V6.2	· Windows 2000 + SP4 is supported. · Windows Server 2003 is supported. · Bugs fixed
V6.1.1	Windows 2000 is supported on the same CD as Windows XP.
V6.1	Windows XP is supported.
V6.0.5 HF2	· V6.0.5 Hotfix 2 also contains Hotfix 1. · WinCC Version 5.1, along with SIMATIC NET V6.0.5, can only be used with Hotfix 2.
V6.0.5	· Bugs fixed · Configured inter-subnet connections
V6.0	· Windows NT, Windows 2000: new, uniform configuration with SIMATIC NCM PC or STEP 7 instead of with a lot of tools (COML S7, COM PB) · Support of the SEND-RECEIVE job AWAIT_CONN_REQ_USER for ISO-on-TCP (synonymous with TCP/IP (RFC 1006)) and ISO
V3.3	· Under Windows 98, access via dial-up networks is possible. · Under Windows NT 4.0, access using RAS is possible. · Windows 2000 is supported.
V3.0	· TSAP routing functionality
V2.0	· Starting several SEND/RECEIVE applications is possible. · ISO-on-TCP (synonymous with TCP/IP (RFC 1006)) can now be called as a Windows NT service.

20.2 Restrictions

PG functions only

The "SOFTNET-PG" product allows operation of PG functions only (STEP 7/STEP 5).

Number of network adapters

A maximum of 1 (one) network adapter with SOFTNET-PG can be operated.

Instructions relating to older modules

Information on the CP 1401, CP 1411 and CP 1511 modules in other documents can be ignored since these modules have been discontinued.

Gigabit Ethernet

Operation of SOFTNET Industrial Ethernet on network adapters with 1 Gbps has not been released.

Link Aggregation, Trunking

The combination of several network adapters to form one "virtual" network adapter is not supported (in compliance with IEEE 802.3ad standard).

20.3 Notes on Configuration and Configuring

Communication using the Remote Access Service (RAS)

A connection to a partner is established with the integrated "RAS" service. The partner only needs to support the establishment of a TCP/IP connection.

If you want to communicate using RAS, your PC must have an ISDN access (for example, ISDN access over ISDN card or router). The TCP/IP protocol must also be installed.

When the ISDN connection is established, the access point of the application is assigned the IP address set during connection establishment or an IP address from the partner. For the RAS mode, set the access point to "S7ONLINE (STEP 7) -> TCP/IP -> NdisWanIp" using the "Configuration Console" dialog (Windows Start menu -> Simatic ‑> SIMATIC NET -> Settings -> Configuration Console).

Message MAC address does not exist in Configuration Console

Network bridge

With a network card that has been added to a "Network bridge" added, it is not possible to operate SOFTNET Industrial Ethernet.

If you want to use a network card inserted in a network bridge for SIMATIC NET products, you must first remove it from the network bridge before installing the SIMATIC NET software product CD.

Deactivated network adapters

When you install the SIMATIC PC software over older versions, deactivated network adapters are reactivated.

21 PROFInet OPC Server

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to Supported Windows Operating Systems"

· Section 25 "Information, Restrictions and Notes Relating to OPC"

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 30 "Notes on Configuration, Configuring and NCM"

You only need to read the other sections if they relate directly to your product.

21.1 Version History

Version	Changes/Additionally Supported Functions
V6.2	· Windows 2000 + SP4 is supported. · Windows Server 2003 is not yet supported.
V6.1.1	Windows 2000 is supported on the same CD as Windows XP.
V6.1	● Bugs fixed ● New data types DATE_AND_TIME for S7 extended variables ● Configuration using STEP 7/SIMATIC NCM PC
V6.0.5 HF2	· V6.0.5 Hotfix 2 also contains Hotfix 1. · WinCC Version 5.1, along with SIMATIC NET V6.0.5, can only be used with Hotfix 2.
V6.0.5	● Bugs fixed ● New data types DATE_AND_TIME for S7 extended variables

21.2 Restrictions

PN OPC server is not released for Windows 2003 Server

The PN OPC server is not released for the Windows 2003 Server operating system because the PROFInet partner devices, CP 343-1 PN V1.1 and the IE/PB Link V1.1 do not support communication over DCOM with Windows 2003 Server.

Delayed recovery function following connection abort

Due to the existing connection monitoring, the PROFInet OPC Server detects a connection abort. The re-establishment of the connection and the change in the quality from "BAD" to "GOOD" can, however, take up to several minutes.

Deleting all protocols except "Connection-oriented TCP/IP" can speed up the re-establishment of the connection.

Follow the steps below under Windows 2000:

Step	Description
1	Open the "Run" dialog via the Windows Start menu.
2	Enter "dcomcnfg" and confirm with "OK".
3	When the "Distributed COM Configuration Properties" dialog opens, select the "Default Protocols" tab.
4	Delete all the protocols except "Connection-oriented TCP/IP".
5	Restart your computer.

Follow the steps below under Windows XP/Windows Server 2003:

Step	Description
1	Open the "Run" dialog in the Windows Start menu.
2	Enter "dcomcnfg" and confirm with "OK". Reaction The "Component Services" dialog box appears.
3	In the left-hand pane of the dialog box, go to "My Computer" in the tree (expand Console Root -> Component Services -> Computers -> My Computer).
4	Right-click on "My Computer" and select "Properties".
5	Select The "Default Protocols" tab in the "My Computer Properties" dialog box.
6	Delete all protocols in the "DCOM Protocols" list box except for "Connection-oriented TCP/IP".
7	Restart your computer.

Use only one subnet per PC station

If there are several subnets (network adapters in the PC station), the PROFInet OPC Server cannot uniquely assign the partner IP address to the network adapter. This means that no connection can be established. The use of several network adapters in a PC station on various Ethernet networks is not recommended.

21.3 Note

Consistency of symbol files

For PROFInet, you can use the iMAP Workbench to generate symbols for the PROFInet variables and store them in an OPC symbol file. You can also display and modify a symbol file with the Symbol File Configurator. Avoid simultaneous access to the same symbol file.

SIMATIC iMap V2.0 uses shorter symbol names.

In previous iMap symbol files, all item names began with "Project...".

An additional prefix could be defined in the "Configuration Console" so that these items had the following structure: "Prefix.Project...".

As of SIMATIC iMap V2.0, a default prefix, for example, "Project" can be assigned per iMap symbol file. Items now no longer have an explicit preceding "Project".

If the recommended default prefix is used with the "Configuration Console", this means a shorter syntax "Project...".

Another prefix or no prefix can, however, also be used. In this case, the item name is shortened. An OPC client must take modified item names into account.

SIMATIC iMap V2.0 does not support symbol files of the type SSD

As of version 2.0 of SIMATIC iMap, only efficient symbol files of the type STI will be created with the "create OPC symbol file" function. We strongly recommend that you use only the STI symbol files to operate the PN OPC server.

Single initialization of the "QualityOf StateValue" parameter with the value of the cycle time.

The "QualityOfStateValue" parameter of the PROFInet configuration file "scorepn.txt" in the section [<connectionname>] has the current cycle time as the default value when an item is first read or written. This value is not changed later, even when the cycle time is changed.

As described, the entered value of "QualityOfStateValue" is used and must, if required, be changed per [<connectionname>].

22 SNMP OPC Server

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to Supported Windows Operating Systems"

· Section 25 "Information, Restrictions and Notes Relating to OPC"

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 30 "Notes on Configuration, Configuring and NCM"

You only need to read the other sections if they relate directly to your product.

You will find the electronic version of the Installation Instructions and other SIMATIC NET documents on the accompanying SIMATIC NET CD "Manual Collection".

22.1 Version History

Version	· Changes/Additionally Supported Functions
V6.2	· Windows 2000 + SP4 is supported. · Windows Server 2003 is supported.
V6.1.1	Windows 2000 is supported on the same CD as Windows XP.
V6.1	Support for Windows XP
V6.0.5 HF2	· V6.0.5 Hotfix 2 also contains Hotfix 1. · WinCC Version 5.1, along with SIMATIC NET V6.0.5, can only be used with Hotfix 2.
V6.0.5	Support for Windows 2000 and Windows NT

22.2 Licenses

As supplied, the SNMP OPC Server Basic includes a license for 20 IP addresses. This allows you to access 20 nodes from a PC.

As supplied, the SNMP OPC Server Extended has no restrictions.

As supplied, the SNMP OPC Server PowerPack is an update of the Basic Version to the Extended Version.

22.3 Examples

ActiveX controls and application samples

ActiveX controls and application samples for the SNMP OPC Server are available on the Siemens Internet pages as FAQs under entry ID 13051333.

German link: http://www4.ad.siemens.de/view/cs/de/13051333

English link: http://www4.ad.siemens.de/view/cs/en/13051333

23 DX OPC Server

Please make sure that you read the following sections in this document:

· Section 24 "Requirements and Restrictions Relating to Supported Windows Operating Systems"

· Section 25 "Information, Restrictions and Notes Relating to OPC"

· Section 26 "Notes on Licenses and Key Diskettes"

· Section 27 "Requirements and Restrictions Relating to Hardware in General"

· Section 30 "Notes on Configuration, Configuring and NCM"

You only need to read the other sections if they relate directly to your product.

23.1 Version History

Version

Changes/Additionally Supported Functions

V6.2

New product for:

· Windows 2000 + SP 3 or SP4

· Windows XP + SP1

· Windows Server 2003

23.2 Restrictions

TargetItemPath and SourceItemPath are not supported

The "TargetItemPath" and "SourceItemPath" parameters are not supported when the "AddDXConnections()" function is called.

Fast changes to a lot of DX status items should be avoided

Fast changes to a lot of "Overridden" and "SourceItemConnected" DX status items at the same time should be avoided. Otherwise this can lead to memory leaks.

23.3 Note

Target items are validated during configuration

When configuring DX connections, the target items are validated, however not the source items. If, for example, the configuration of the OPC name space is not yet loaded on the PC station, DX connections will be rejected at the "AddDXConnections( )" call. The PC station should therefore be configured with STEP 7 before the OPC DX configuration.

DX sample client from the OPC Foundation

No sample client is supplied with the DX OPC server product. The OPC Foundation www.opcfoundation.org provides a sample client including source code.

Trace files are overwritten when the computer restarts

If you want to create trace files for diagnostics for OPC DX in the "Overwrite" mode, make sure that the trace file is also renamed as a backup file when you restart the computer, for example, "opc‑dx.lo~", and that a trace file is created.
In this case, use the backup file or create trace files in the "Append" mode.

Writing items singly

The following items of a DX connection can be written at the same time over the Status item: (SourceItemConnected, TargetItemConnected Overridden, OverrideValue).

In this case, no deterministic behavior or order can be expected of this function.

Write the values singly.

Avoiding overlapping target addressing

Overlapping target addressing, for example MB1 and MW0 should be avoided since a check only checks for the same addressing of target items on different DX connections.

Delays due to timeouts when writing to the target

Targets of OPC DX connections are written synchronously. If timeouts occur when writing target items, for example due to a protocol interruption on a connection to a partner, the writing of other targets on other DX connections will be delayed and can only be processed on completion or timeout of the previous write.

Same target items

If there are DX connections to the same target items and different source items, the DX connections established first wins.

DX items are case-sensitive

DX items and connection names are case-sensitive. Remember that SIMATIC NET OPC DA items are not case-sensitive.

DX target items are read only

DX target items are read-only although the access permissions of the item displayed with OPC-DA ("RW") do not indicate any restriction.

24 Requirements and Restrictions Relating to Supported Windows Operating Systems

24.1 Supported Operating Systems

Usable operating systems

The products of this SIMATIC NET PC software can be operated with the following operating systems:

· Windows XP + SP1 ‑ Professional

· Windows Server 2003 (Windows Server 2000 Standard Edition)

· Windows 2000 + SP3 or SP 4 ‑ Professional, Server, Server with terminal service functions

· Of the Chinese language versions, only the language version "Simplified Chinese" is supported, however not in the Multilanguage versions of Windows.

The service packs listed are necessary! You will find service packs for Windows 2000 or XP on the Microsoft home page as downloads.

Only one operating system per computer permitted

SIMATIC NET PC software products are supported only on computers on which one operating system and one only is installed. Computers with multiple selectable operating systems are not permitted.

24.2 Terminal services with Windows 2000 and Windows Server 2003

Description

The use of the terminal services of the Windows 2000 Server with a terminal service client for SIMATIC NET products is released as of SIMATIC NET Software Products CD 07/2001 SP5.
The use of the terminal services of Windows Server 2003 with a terminal service client for SIMATIC NET products is released as of SIMATIC NET Software Products CD 11/2003.
This means that all work with SIMATIC NET PC software products can be performed via a Windows 2000/ XP‑Terminal. Possible conflicts due to connecting several terminals have been eliminated. For a terminal user, this means:

· Programs for configuring and assigning parameter values for the SIMATIC NET software such as "Configuration Console" or "Station Configuration Editor" can be operated at the same time from one terminal.

· Messages from SIMATIC NET products (error messages, run-time messages) are displayed on all logged on terminals.

Installation of SIMATIC NET PC products

Please note that Setup switches the Windows 2000 Server/Windows Server 2003 with installed terminal services to the "installation mode" from the "user mode" during installation of SIMATIC NET PC Products.

Once the installation is successfully completed, the server continues in the user mode again after you restart.

Further information

You will find wide-ranging help on the terminal services in the help system of the Microsoft Windows 2000 Server/Windows Server 2003.

Restrictions affecting configuration

It is not possible to configure with the SIMATIC NET PC Manager and the PC Station Wizard in SIMATIC NCM PC on terminal service clients.

Programs started from a remote terminal client can hang for several seconds

If you start an application on a terminal server from a remote terminal client, this may hang for several seconds if the connection between the terminal client and terminal server is disrupted or the terminal client computer changes to the sleep mode.This can lead to temporary computer blockages of several seconds on the terminal server if the communication connection between the PC/PG and terminal is interrupted.

24.3 Restrictions

The following functionality is not supported because of potential problems during operation with SIMATIC NET:

· The files must not be encrypted (for example NTFS5 Encrypted File System). This applies to all files required for the functionality of the CD (program files, configuration files, databases etc.).

· Files installed by SIMATIC NET must not have the "hidden" or "superhidden" status.

· The on-demand installation of the SIMATIC NET software using Windows 2000 Server/Windows Server 2003 is not possible.

· It is not possible to assign UNC path names for databases or programs of SIMATIC NET.

· User programs that communicate using SIMATIC NET must not be used as Windows services (background processes) and must not be triggered in the Autostart group to avoid undefined initialization statuses during startup.

The following functions are not released because they have not been tested:

· It is not possible to install on replaceable disks or enlarged hard disks ("DFS").

· Installation in a folder that references other drives (known as "junction points") is not supported.

· The "Disk Quota" property is not supported; in other words, if you have set a maximum value, this could nevertheless be exceeded when you install SIMATIC NET software.

· The CP 1613 module for Industrial Ethernet must not be operated with IPSec.

· The CP 1613 module for Industrial Ethernet must not be used in VPN (Virtual Private Networks).

24.4 No Real Time

Windows is not a real-time operating system. Real-time requirements cannot therefore be met.

As a result, it is possible that when starting programs or reading files, your application is not executed for several 100 ms.

The points below will help you to optimize your system and to achieve reaction times approaching those of a real-time system:

· You should have enough memory so that Windows only seldom needs to use the page file.

· Avoid intensive access to diskettes, hard disks, or CD drives such as occurs when starting up large programs.

24.5 Further Notes

Restoring files

When Windows XP/Windows Server 2003 prompts you to insert the Windows CD to restore files, follow the instruction and confirm with "OK".

Installation of Chinese

The installation dialog of the SIMATIC NET software offers you the choice of German or English. If you want to install on a Chinese Windows platform, select English.

Required privileges

Under Windows, you must have power user or administrator privileges to start the software tools "Set PG/PC Interface" or "Configuration Console".

To work with NCM PC under Windows, you must log on at least as power user. To install SIMATIC NCM PC and to set up modules using the "Set PG/PC Interface" application, you must have administrator privileges.

Upgrade to newer Windows operating systems

If you upgrade from Windows NT 4.0 or Windows 2000 to Windows 2000 or XP or /Windows Server 2003 you must first uninstall all the SIMATIC NET products. After uninstalling the products, you can then upgrade to the new Windows version. The SIMATIC NET PC software can then be installed.

System settings for ActiveX controls and Java Script

ActiveX and Java script are used in the HTML document "Industrial Communication for PG/PC" (MN_OPC_0.chm or MN_OPC_76.chm). It is advisable to select the settings in the Microsoft Internet Explorer so that this is supported. Only then can you use the full functionality of the online documentation.

DCOM error in the Event Viewer

The configuration of a PC station with PCS7/APACS + option V6.0 replaces the DA0350.DLL from version 3.50.3602 with version 3.51.1608.0. As a result, the Event Viewer displays the message "DCOM Error" every two minutes for the SIMATIC NET Configuration Server and SIMATIC NET Configuration Service.

DCOM settings and MSI installation for Windows 2000

If you have modified the default DCOM settings as described in the HTML document "Industrial Communication for PG/PC", so that you can communicate with the DCOM OPC Server, you cannot install/uninstall any further MSI-based programs. This restriction does not, however, apply when you install a SIMATIC NET PC Product CD or a new service pack.

If you need to do this, you must change the standard DCOM settings for the time of the installation. Follow the steps below:

1. Note down the settings made on your PC for the parameters "Default Authentication Level" and "Default Impersonation Level" (taskbar Start -> Run -> dcomcnfg and open -> Default Properties -> tab, dialog section Default Distributed COM Communication Properties).

2. Set the parameters as follows:

Parameter	Setting
Default Authentication Level	Connect
Default Impersonation Level	Identify

It is now possible to install/uninstall a further MSI-based program. SIMATIC NET applications that communicate using the DCOM server, are, however, no longer fully functional.

3. Set the original settings for the "Default Authentication Level" and "Default Impersonation Level" again.

Trace paths

Storage space for trace paths must be set up for all users with write permissions.

25 Information, Restrictions and Notes Relating to OPC

25.1 OPC as Standard Interface

The SIMATIC NET software products have access via OPC as the default interface. The user can therefore has standardized access options for all protocols of these products.

25.2 Restriction with OPC

No OPC communication and configuration possible after uninstalling WinCC V6.0

After uninstalling WinCC V6.0, it is no longer possible to configure with the "Configuration Console" and OPC communication is no longer possible. To remedy this, (over)install the SIMATIC NET PC Software CD again.

OPC Data Access interface V3.0 is not released

The OPC Data Access interface V3.0 is not released for the SIMATIC NET OPC DA server although the server is registered for this category and the appropriate methods already exist.

Automation Interface for Alarms and Events not yet available

The Automation Interface for Alarms and Events described in the documentation supplied with the SIMATIC NET CD is not yet available in this version of the SIMATIC NET PC software.

"SIMATIC NET Data OCX" not released for VBA and VBS

The "SIMATIC NET Data OCX" control is not released for use in Visual Basic for Applications (VBA) and Visual Basic for Scripts (VBS).

Errors can occur in the following situations:

· Color selection dialogs cannot be opened.

· When closing Excel, the error message "Application Error" appears often.

Note:

The control has, however, being released for Visual Basic applications.

Configuring access permissions for OPC items

Restriction up to SIMATIC NCM PC / STEP 7 V5.1 SP 2:

Using item-specific permissions when using several protocols at the same time is possible only with certain restrictions.

If the permissions are configured for several protocols in SIMATIC NCM PC/STEP 7, these settings will only be applied for one of these protocols; in other words, the other protocols ignore the configured permissions.

This restriction applies only to the situation when the configuration was downloaded directly from SIMATIC NCM PC / STEP 7; supporting the configuration using an XDB file eliminates this problem.

Changed error code if an empty string is used as ItemID

The OPC DA Server as of the SIMATIC NET Software Product CD V6.0 + SP4 returns the following error code in keeping with the extended standard OPC DA 2.05 when an empty string is entered for the ItemID:

0x80070057 ("bad parameter").

Previously in this situation

0xC0040007 ("unknown item") or

0xC0040008 ("invalid item") was returned.

FMS protocol for OPC: Using the same item as index and symbolic name

If the same item is used as an index and as a symbolic name before the remote object dictionary has been loaded on an FMS connection, it can only be inserted once in an active OPC group.

SEND/RECEIVE TCP connections with the CP 1613 over OPC

SEND/RECEIVE TCP connections over the CP 1613 can be configured as of STEP 7 V5.1 SP4, however it is not possible to select the NDIS IP address. You should therefore not use SEND/RECEIVE TCP connections over OPC with the CP 1613.

(Note: TCP connections identify connections of the type TCP/IP native; in other words without RFC 1006).

As of STEP 7 V5.2, the above restriction no longer applies.

Tag files with extended variables

Tag files with S7 variables generated with iMAP V1.0 are no longer supported if the iMap V1.1 project has been downloaded to the hardware.

To ensure consistency, symbol files generated with iMap and suitable for the current iMap project should be used.

OPC Scout: Duplicate alias names

In the OPC Scout, it is possible to enter duplicate alias names within a branch. To avoid alias names being overwritten, please make sure that they are unique.

No buffer send/receive services for unconfigured S7 connections to an S7-CPU

For unconfigured S7 connections, no buffer send/receive services (BSEND/BRCV) can be used because these require S7 connections to an S7-CPU to be configured at both ends. Nevertheless, OPC BSEND/BRCV items, for example, in the OPC Scout, can be added without an error message.

No data reporting after changing from "Connect" to "Default" in DCOMCNFG

After changing the Default Authentication Level from "Connect" to "Default" in the "DCOMCNFG" configuration program, no more data is reported via OPC.

To work with DCOM, please follow the instructions in the HTML document "Industrial Communication for PG/PC".

German umlauts (ä, ü, ö etc.) with a Chinese operating system

Umlauts in the German HTML document "Industrial Communication for PG/PC" are not correctly displayed with a Chinese operating system (Windows 2000 Server Multilanguage/Windows Server 2003, Chinese settings).

Delayed access to the OPC Server immediately after logging on with the operating system or while downloading a new configuration

After logging on with the operating system or during configuration, various different processes are started. This can delay access to the OPC Server.

This delay can lead to error messages in the OPC Scout that are misleading since they suggest incorrect DCOM settings.

Delayed access to a high number of OPC-FMS variables

If you access the maximum possible 5 local FMS-VFDs each with approximately 850 local variables, you may experience delays on the screen of several seconds or even minutes when you open a group in the OPC Scout.

FMS variables cannot be inserted

The FMS variables of a remote partner cannot be inserted using OPC is the connection to the remote partner cannot be established.

Writing negative values of items of the data type DWORD

If, for example, items of the data type DWORD are written with negative values, for example starting at -255, with the OPC Scout using the "Generate values" function, the error E_RANGE is not returned. Internally, the VariantChangeType operating system function is used that converts a negative string value (VT_BSTR) to an integer and interprets it as an unsigned value and it is then written as such.

For example, "-255" is converted to 0xFFFFFF01 = 4294967041 and written.

You should therefore always take into account the interpretation of a data type.

CP 5511, CP 5512, and CP 5611 communications processors as PROFIBUS DP slaves

The communications processors CP 5511, CP 5512 and CP 5611 can be configured as PROFIBUS SOFTNET-DP slaves. If you use OPC as the interface, SOFTNET‑DP slave submodules must not have any "special ID formats" in the configuration.

Check the configuration of each SOFTNET-DP slave submodule in HW Config. It must contain no "special ID formats". If "special ID formats" exist, you can recognize this because the parameters "Output length byte" and "Input length byte" in the "Direct input" dialog box are displayed in gray (You can display these parameters as follows: Select the SOFTNET-DP slave with the mouse in HW Config -> select Slave Submodule with the right mouse button -> select Object Properties -> click the Direct Input... button in the "Properties DP Slave" dialog box).

Memory leaks on the OPC server with symbols of the type SSD when repeatedly connecting, browsing and disconnecting on extra connection

If you have an OPC server connection and repeatedly establish and close a further connection and browse for items of the type SSD in symbol files, you will increasingly lose memory the more often you do this.
Avoid establishing extra connections, browsing and then closing the connection again. Use the new symbols of the type STI.

100 % CPU utilization with OPC Alarms and Events leads to memory leaks

At 100 % CPU utilization of the OPC Alarms and Events server, no memory can be released. Avoid this high utilization.

Support of bit arrays

OPC supports S7-bit array items with restrictions. Downloading symbolic OPC‑bit array items is not possible.
The following restrictions apply to bit array items:
The array must begin at element 0 and the array size must be a multiple of 8.

Storage of the XML file

As of SIMATIC NET V6.1 SP1, the XML file exported by the SIMOTION Scout must be stored in the following folder on the destination drive in the installation path of SIMATIC NET:

<Installationspfad von SIMATIC NET>\opc2\bins7\simotion\xml\opc_ae.xml

Unsuccessful downloading of S7 symbols to PC station

If no symbolic OPC items can be selected or added after downloading a STEP 7 project with S7 symbols, there may have been a download error that is not displayed.
Check the STEP 7 project for consistency and repeat the download.

Symbol File Configurator: Avoiding special characters in folder names

When working with the Symbol File Configurator, avoid the following special characters in the folder name of a symbol file:

· Square bracket open ( [ )

· Square bracket closed ( ] )

· Pipe ( | )

· Exclamation point ( ! )

Otherwise subfields can no longer be browsed.

Symbol File Configurator: Changing folder names no longer possible

It is no longer possible to change folder names in the Symbol File Configurator.

OPC Scout: Unconfigured connections "Read in new"

Newly created unconfigured connections can only be seen in the browser of the OPC Scout when the items have been updated with the "Read in new items from here" context menu.

Time base and range of values for S7 timer variables (type T):

The range of values of OPC process variables for S7 of the type timer (T) is coded in milliseconds in decimal and not BCD coded with a time interval as stated in the manual.

Multiples of 10,000 ms, 1,000 ms, 100 ms, and 10 ms determine the time base in this order. The ranges of values are obtained from this time base and a factor of 1 through 999:

Possible values	Time Base	Comment
1,000,000 ms through 9,990,000 ms	10 s	The values must be a multiple of 10,000 ms.
100,000 ms through 999,000 ms	1 s	The values must be a multiple of 1,000 ms.
10,000 ms through 99,900 ms	100 ms	The values must be a multiple of 100 ms.
10 ms through 9,990 ms	10 ms	The values must be a multiple of 10 ms. Smaller increments are not possible. 0 ms is permitted but has no function.

Clearly the number of zeros to the right decides the time interval, the leading numbers from 1 through 999 multiplied by the time interval decides the operating time.

OPC XML Web service: PROFInet byte array returns "E_BADTYPE"

When accessing OPC XML items of the PROFInet byte array data type "VT_ARRAY|VT_UI1", the error "E_BADTYPE" is returned for the "GetProperties" or "Browse" call.

No browsing in the Symbol File Configurator if only the DP, S7 or SR protocols are active

If you only use the powerful OPC server for the DP, S7, SR protocols, if an OPC client is already in operation it is no longer possible to browse at the same time when adding new symbols with the Symbol File Configurator. To be able to browse, close the OPC client.

Configuration Console: "Server busy" message window with very large symbol files

If very large symbol files containing tens of thousands of symbols are selected under Windows 2000 in the "Configuration Console", a message window "Server busy" may be displayed several times in the "Manage Symbol Files" dialog. This action takes several seconds and no hourglass is displayed.
Click on the "Retry" button of the message window and not on the buttons of the "Manage Symbol Files" dialog otherwise the program can no longer be controlled.

No OPC alarms and events compliance tests performed

No OPC alarms and events compliance tests were performed for the "OPC.SimaticNetAlarms" and "OPC.SimaticNetAlarmsSNMP" servers.

25.3 Note

Downloading S7 symbols with NCM version V5.2

If you use symbols on S7 connections, new symbol files can be created automatically using NetPro in STEP 7 V5.2 or higher and downloaded to the PC station.

Please wait while downloading tens of thousands of S7 symbols

The downloading of OPC server project engineering data from STEP 7 with tens of thousands of S7 symbols can take several minutes. Please wait until complete.

High performance with new symbol files of the type STI

The use of the new symbol files of the type STI achieves a significantly better performance when accessing the symbol file.

If you have bowled symbol files of the type SSD or WSD, we recommend that you convert these using the new Symbol File Configurator 2.0 and activate them in the "Configuration Console" configuration program.

Further note:

If you use symbols on S7 connections, new symbol files can be created automatically using NetPro in STEP 7 V5.2 or higher and downloaded to the PC station.

OPC Automation Interface

The OPC Automation Interface for OPC Data Access has been released in a version from Siemens in which the errors have been corrected and is based on the version provided by the OPC Foundation.

Trace settings for the OPC Alarms and Events Server

The OPC Alarms and Events server has changed trace settings as of V6.0.2. The same settings can now be made for the trace as for the OPC Data Access Server. Following installation, please check the trace setting.

Time stamp of Alarms and Events messages

In the current version, the time stamps of Alarms and Events messages are transferred by the device that triggers the alarm. However, in this case, the local time of the remote system is given and not the UTC time. If you require UTC time, set the UTC time as the local time on the remote system.

OPC Scout: Connections configured with iMAP visible in /SYM and /S7

As soon as a connection configured with iMAP is monitored in the OPC Scout and a second OPC Scout is started, this displays the S7 connection of the symbol file in the /S7 path as well. The connection name is the name specified during configuration with iMAP.

OPC Scout: Inserting items in groups

Items, that are syntactically or semantically incorrectly structured, are shown in a browser but cannot be inserted into groups.

OPC Scout: Remember the maximum number of connections

The maximum number of connections must not be exceeded. The OPC Scout would appear to be inoperable because setting up would take extremely long (in some circumstances even days).

OPC Scout: input format for writing values is a character string

The OPC Scout uses strings as the input format for writing values and these are then converted by the OPC server depending on the type. A conversion, especially with language-dependent data types such as VT_R4, VT_R8 and VT_DATE is not always possible. In this case, use an OPC client that allows input of the correct type.

FMS strings are padded out automatically

If less characters were transferred with a string defined as having a specific length, all other characters had to be padded out with blanks by the user. When using the FMS-OPC Server V6.0 or higher, this padding is done by the OPC Server automatically.

Avoiding interruptions on connections

With passive connection establishment, the connection monitoring (see Error Timeout for OPC Jobs during Operation) can cause the connection to be closed. To avoid the connection being closed, we recommend that you configure an active connection establishment in STEP 7. You may need to adapt the connection monitoring times.

Avoiding loss of memory caused by invalid items

If you insert OPC items in a group when several protocols are active or when using symbols and the response is an error code, in some cases, not all resources of the OPC server are released. Repeated attempts to insert an unknown item in a group can therefore lead to the resources of the operating system being totally used up so that the computer is no longer operable.

If you have attempted to insert items in a group several times, you should close the OPC server before you make any further attempts. Generally, the OPC server closes itself as soon as no OPC user program is accessing it any more. You can, however, also close the OPC server explicitly using the "Configuration Console".

It is advisable, to avoid repeated insertion of invalid items or to select a repetition rate higher than 1 minute so that there is no loss of resources.

Speeding up connection establishment in FMS when using client and server

Depending on the characteristics of the partner device, both loading an object dictionary or activating a configured local object dictionary can take a considerable amount of time.

If the FMS OPC Server is operated as an FMS client and FMS server at the same time with its own object dictionary configured in SIMATIC NCM PC, connection establishment can be considerably delayed or even not take place at all.

In this case, it is advisable to load the relevant object dictionary using the "ODUpload.exe" program for the for the FMS client functions; in other words, the monitoring of remote FMS variables.

For more information on working with the "ODUpload.exe" program, please refer to the FAQs on OPC, title "Establishing the FMS connection to partners with a large object dictionary takes such a long time that the startup of the system is delayed considerably." Is there a way to avoid this? document "Industrial Communication for PG/PC Manual".

Demo connection hides real configured connection with the same name

If you activate the Demo mode for a protocol under "CP Simulation" in the "Configuration Console", a connection with the name "DEMO" is displayed automatically in the browser of the OPC Scout. If you have configured a real connection with the same name in a STEP 7 configuration and downloaded this successfully to the PC station, the connection will be hidden.

As a result, when "CP Simulation" is inactive, you see a real connection with the name DEMO, and when "CP Simulation" is active, you still see a connection with the name DEMO in the browser, however this is then only the DEMO connection and the real connection is not visible.

This also applies to the (connection) name SYSTEM under which information variables such as &version() are displayed.

Changing from configured operation to PG operation during communication is possible

If a module is switched from configured operation to PG operation using the "Configuration Console" program or the "Station Configuration Editor", this occurs without any further warning or message to a user program that may currently be communicating via the module.

Incorrect help page in the "Microsoft Management Console"

If you select a help page in "Microsoft Management Console" in the German online help for the "Configuration Console", the page is not displayed. The problem is in the general help file of the Management Console of Microsoft.

Hidden message window of the Management Console

When you close the Management Console, and have not saved all the changes, a message window sometimes appears with the prompt "Do you want to apply the new settings?" after you have closed the main window. The text in the title bar of the message window indicates the dialog in which you have not save the last changes.

Entry in the event log after a bad remote symbol download

If errors occur during a remote symbol download, there is neither an entry in the diagnostic buffer of the Station Manager nor a message box in STEP 7 to inform the user that problems occurred during the download of the symbols.

An entry is made in the event log of the remote operating system. This entry can also be read out remotely from the event log from the configuration computer.

Error messages and how they are interpreted with FETCH and WRITE when using SEND/RECEIVE

If you use the SEND/RECEIVE OPC Server, the error messages listed below relating to the FETCH and WRITE operations can have the following causes:

Error Message Text

Cause

The required operation (read or write) is not permitted by the access rights of the item

1. You have no rights (normal situation)

2. DB (data block) or PB (I/O module) does not exist.

3. The area exists (BS, I, Q, M, PB, T or C) but is addressed outside the maximum permitted area limits.

Unexpected communication error

1. Bus cable not plugged in (normal situation).

2. Other communication error (normal situation).

3. DBs or PBs are addressed outside the existing limits.

Adopting the OPC protocol settings takes several seconds

Adopting the OPC protocol settings in the "Configuration Console" program can take several seconds.

If the address space is browsed in the Symbol File Configurator while these settings are being adopted, due to the delay too many or too few protocols may be displayed during this time.

Recommended settings for the timeout parameter for S7 connections and fault-tolerant S7 connections (S7-REDCONNECT)

The configurable "Connection establishment timeout" should be significantly longer than the possible minimum value of 2000 ms, for example 15,000 ms (default) to give the entire system time if a disturbance has to be dealt with.

The OPC connection parameter "Timeout for OPC jobs during operation" in STEP 7 NetPro should be selected according to the reaction times of the entire system to avoid detection of disturbances from becoming too sensitive; default 15,000 ms.

SIMATIC NET OPC protocol servers will be operated as system service as of software version V6.0.5

With the aid of the "Computer Management Services", their properties and operating mode can be configured. By operating as a system service, consistent multiterminal capability is possible with the operating systems Windows 2000 Server, Windows XP and Windows Server 2003.

For DCOM operation of the SIMATIC NET OPC protocol servers, this results in the restriction that the "SYSTEM" user must be added to the default access rights in the DCOMCNFG application in addition to configured users to allow OPC callback functions to be executed.

Restriction regarding the security authentication with the OPC client in DCOM operation

If the connection establishment between the OPC client and remote OPC server is declined in DCOM operation within a Windows workgroup, the security authentication may be the cause of the refusal. In this case, it can be useful to restrict the security authentication.

A fixed security setting can be achieved using the CoInitializeSecurity( ) function call. Insert this into your OPC client program as follows:

CoInitializeSecurity(

NULL, -1, NULL, NULL,

RPC_C_AUTHN_LEVEL_NONE,

RPC_C_IMP_LEVEL_IDENTIFY, NULL, EOAC_NONE, NULL);

This sets the "authentication level" to "none", the "impersonation level" to "identify".

This call must take place prior to connection establishment with CoCreateInstanceEx( ).

The programmed setting of the security level dominates the setting made with the "DCOMCNFG" configuration program.

You should remember this even with non self-programmed OPC clients.

Connection establishment can nevertheless take several seconds despite restricting the security level.

SNMP error message but irrelevant

Although no SNMP item is selected, an error message "SIMATIC NET Synchronization Server - SIMATIC NET Core Server SNMP Protocol libraries not found on computer" can be displayed. This error message can be ignored.

Timeout exception when calling the XML-DA Web service

If a job sent to the XML-DA Web service fails with a timeout, a SOAP FAULT is generated that leads to an exception on the client. The cause of the exception (timeout) cannot be identified.

Writing invalid values with OPC XML-DA-Web services

When writing an invalid value with OPC XML-DA-Web services based on RC1.8, the current and still valid value of the variable is not returned with the acknowledgment. A further read job is necessary to obtain this value.

Assigning permissions for using symbol files with the OPC XML-DA Web service

The OPC XML-DA Web service uses the following additional services to allow use of the configured symbol files:

· under Windows 2000/XP, the ASP.NET services.

· under Windows Server 2003, the network services.

Please assign read and write permissions to these services for the folders in which the STI or SSD symbol files will be stored.

When browsing symbols using the OPC XML-DA interface, the error "0xC00481FF - E_SERVER_DOWN" occurs sporadically; please repeat your browsing.

When browsing a symbol file without the required permissions and with default prefix, the value E_FAIL is returned and without prefix, the value S_FALSE.

MSDE-OPC-XML-DA clients must use the local time and not UTC time

OPC-XML-DA clients developed with the Microsoft Development Environment 2003 must transfer the local time not UTC time as "RequestOptions.RequestDeadline". The "Standard SOAP Writer" of Visual Studio 2003 always converts the transferred time to a UTC time in the format "localtime + time offset".

Optional OPC XML-DA function parameters must be set to "Specified = true"

Values that are not transferred as mandatory values in OPC-XML-DA calls, can only be used when "Specified = true" is set.

Example: MaxAge.

If the "MaxAge" parameter needs to be transferred, "MaxAgeSpecified = true" must be set otherwise the value is ignored.

Async2RefreshDevice also returns "write-only" items

Calling the Async2RefreshDevice function of the OPC Automation interface returns all items including "write-only".

Adding existing symbols in the Symbol File Configurator

In the Symbol File Configurator, you can select and name several symbols using the "Insert New Symbols" menu command. Names you have already assigned are not added and a message is displayed. This message does not tell you which of the symbols could not be added.
Add only one or a very few symbols at any one time. Check that names of symbols you are adding are unique and save regularly.

Symbol File Configurator - Periods converted to underscores

In the Symbol File Configurator, you can select and name FMS symbols using the "Insert New Symbols" menu command. A symbol name is proposed that is derived from the runtime name. Please note that periods are then converted to underscores.

Error messages for the OPC protocol multiplexer

Error messages for the OPC protocol multiplexer are not described in the "Industrial Communication with PG/PC" manual.

Alarm categories table in the manual

The "Alarm Categories" table in the "Industrial Communication with PG/PC" manual, Section 5.1.1. contains SIMPLE events for the categories EVENTCATEGORY_S7SIMPLE, EVENTCATEGORY_S7TO, EVENTCATEGORY_DIAGNOSIS and EVENTCATEGORY_STATEPATH.

CONDITION events are supported by the EVENTCATEGORY_S7CONDITION category.

Browsing with negative "MaxElements" value with the OPC XML-DA Web service

It is possible to specify a negative "MaxElements" when browsing because the value is of the "int" type.

If a negative MaxElements is specified an exception occurs.

Rounding error in OPC XML DateTime items

When writing/reading "DateTime" items with OPC XML and "OPC.NET", errors up to 2 ms can occur caused by the .NET Interop layer.

Download check box must be set for S7 symbol download

If the check box "Use as target for S7 symbol download" is deactivated in the "Configuration Console" program, "Manage Symbol Files", the download from STEP 7 will be rejected. The OPC server component cannot be started.
If you have configured S7 symbols, please do not deactivate this check box.

OPC XML Web service "Liste.RequestedSamplingRate"

If "Liste.RequestedSamplingRateSpecified" is set to true and a senseless value is entered that is nevertheless above the minimum value, "Liste.RevisedSamplingRateSpecified" becomes false and "RevisedSamplingRate" is set to 0 and the expected correct value is returned for "Liste" for "Liste.Item[0].RevisedSamplingRate".

The value is not passed to "Liste.RevisedSamplingRate" and "Liste.RevisedSamplingRateSpecified" is not set to true.

OPC XML Web service "RequestOptions.ItemName"

When parameter "RequestOptions.ItemPath" is set to "true" or "false", the ItemPath in the path is returned and not zero.

Avoid multiple import of csv files

When importing csv files, you should save the file after each import. If you import several times in succession, the import can hang without an error message being displayed. Save after each csv import.

OPC XML Web service: Symbol file not interlocked

If the OPC XML Web service has no write permissions in the storage folder of a configured symbol file of the type STI, access to this is not interlocked during operation. The symbol file can be modified and saved in the Symbol File Configurator.

Adding Internet Information Services (IIS) under Windows Server 2003

Follow the steps below to install the Internet Information Services (IIS) in Windows Server 2003.

1. Click on the "Add/Remove Windows Components" button in the Control Panel (taskbar Start -> Settings -> Control Panel -> Add/Remove Software -> Add/Remove Windows Components).

Reaction: the "Windows Components" dialog box of the "Windows Components Wizard" appears.

2. Select "Application Server" in the list box and click on "Details".

3. Here, select "Internet Information Services (IIS)", "Enable COM+ Network Access" (selected automatically) and "ASP.NET".

4. Confirm with "OK".

5. Confirm with "Next" and install the component.

Assigning permissions for creating trace files of the OPC XML-DA Web service

The OPC XML-DA Web service uses the following additional services to create trace files:

· under Windows 2000/XP, the ASP.NET services.

· under Windows Server 2003, the network services.

Please assign read and write permissions to these services for the folders in which the trace files will be stored.

Vendor-specific OPC error "E_ITEMPATHUNSUPPORTED"

If an item path is specified for use with the OPC XML-DA Web service, the vendor-specific OPC error "E_ITEMPATHUNSUPPORTED" is displayed.
The OPC errors E_INVALIDITEMPATH and E_UNKOWNITEMPATH are no longer supported.
The OPC error "E_ITEMPATHUNSUPPORTED" currently returns the following error messages:

"The item path is no longer available in the server address space."

Displaying access permissions of symbolic items in the OPC Scout

A read-only item, for which a symbol with RW access permission is created in the symbol is displayed with the access permissions RW in the OPC Scout. If, however, this symbol is inserted in a group, the access permission R is displayed correctly.

AddItems( ) allows a maximum of 32767 items per group in multiprotocol mode

If more than one protocol is selected, only a maximum of 32767 items can be added per OPC group with the OPC-DA function AddItems( ). If only one protocol (even with additional symbols) is selected, this restriction does not apply.

25.4 OPC Client Setup for DCOM Operation

Range and purpose of the software package

If you only want to access remote SIMATIC NET OPC Servers in the intranet, you do not need to install the complete SIMATIC NET software products CD. In this case, you only need to install the OPC client set up for DCOM operation.

Installation for DCOM operation

For DCOM operation, a minimum installation is required on the client computer. This involves installing and registering the required components provided by the OPC Foundation and the OPC Scout.

Following installation, DCOM operation must be set up. For more information, refer to the relevant to chapter in the "Industrial Communication with PG/PC" manual.

To install the software for the OPC client computer, follow the steps outlined below:

Step	Description
1	Start your computer.
2	Log on as administrator with the Windows system.
3	Insert the SIMATIC NET PC software CD in your CD-ROM drive. If the SIMATIC NET CD installation program starts automatically, please close it down immediately (the required installation cannot be made with it).
4	Start the "Setup.exe" program from the "\sw\opc_client\disk1" folder.
5	Enter the name of the computer on which the OPC Server will be started.
6	When you have completed the installation, you must then set the DCOM configuration as described in the manual.

26 Notes on Licenses and Key Diskettes

26.1 Meaning of the License

As long as a license to use this software has not been obtained, this software only runs in its demo mode. Therefore each end user is granted a free, non-exclusive and non-transferable license to use the software in its demo mode. The end user is not entitled to copy, pass on or distribute this software. Furthermore the end-user is not entitled to decompile or modify the software or to link it into other programs. The use of this software in its demo mode is at the end-user's own risk. Since the software in the demo mode is distributed free of charge, the authors are only liable in case of intent or gross negligence. The software is provided "as is" without any representation or warranty of any kind either expressed or implied including but not limited to implied warranties for merchantibility or fitness for use.

AS LONG AS THIS PROGRAM ONLY RUNS IN ITS DEMO MODE, IT IS ONLY MEANT TO BE AN EXAMPLE FOR THE FULL-VERSION OF THE PROGRAM. IT IS NOT MEANT TO BE USED IN CONNECTION WITH LIVE MACHINE OPERATIONS. ANY SUCH USE IS AT THE USER'S OWN RISK.

26.2 Key Diskette

(Does not apply to the product CP 5613/CP 5614 (DP Base) )

You require a key diskette (authorization diskette) for each of the SIMATIC NET software products. This diskette contains an authorization key required to operate the product. A key diskette can also contain licenses for several products. During installation, this key is transferred to the hard disk of the destination system. The products cannot be operated normally without the authorization key. In emergencies (loss of the authorization diskette), the software can be operated and messages are displayed indicating the absence of the license. If an error occurs (a problem with the authorization diskette) please contact our hotline.

The version numbers of the key diskettes (Key Version - KV...) do not relate to the version numbers of the products.

26.3 Important Notes on Handling Key Diskettes and Licenses

Note the following:

· The key diskette must not be write-protected! (standard setting of the write protect slide on the diskette).

· It is not possible to make a backup of the key diskette.

· The licenses are stored in the hidden folder "\ax nf zz" on the drive you specified during installation.
Do not delete the "\ax nf zz" folder or any files it contains.
If you want to reformat your hard disk, you must first transfer the licenses back to the original key diskette using the "AuthorsW.exe" program. If you do not transfer the licenses back to the key diskette, you will lose the licenses and can no longer use the product. When you transfer the licenses back, make sure that you insert the same diskette from which you originally installed them.

· It is not possible to transfer the licenses by simply copying them from the hard disk to a diskette or from diskette to hard disk.

· If you uninstall SIMATIC NET products with an uninstaller that uninstalls programs in Windows, you may lose the licenses.
If you want to uninstall these products with the uninstaller, you must first transfer the licenses back to the key diskette using the "AuthorsW.exe" program. If you do not remove the licenses, the uninstaller may destroy the licenses for these products.

· If you want to reformat your hard disk, you must first transfer the licenses back to the key diskette using the "AuthorsW.exe" program (Windows Start menu -> SIMATIC -> AuthorsW -> AuthorsW). If you do not transfer the licenses back to the key diskette, you will lose the licenses and can no longer use the products.

26.4 Installing and Uninstalling Licenses at a Later Point in Time

Make sure that you transfer the licenses back to the original key diskettes.

Installing licenses later

With the "AuthorsW.exe" program on the supplied SIMATIC NET Software Product CD (also available as download), you can also install licenses later. "AuthorsW.exe" can be started from the Windows Start menu SIMATIC ->AuthorsW ->AuthorsW.

You can also install the "AuthorsW.exe" program later from the SIMATIC NET Software Product CD by starting the Setup program again and selecting "AuthorsW" for installation.

Uninstalling licenses

You can uninstall licenses at any time with the "AuthorsW" program. This assumes that you installed the AuthorsW program.

Follow the steps outlined below to transfer licenses from the hard disk to the license diskette or diskettes (uninstalling licenses):

· Insert the authorization diskette in drive A:

· Start the "AuthorsW" program (taskbar Start -> Simatic -> AuthorsW -> AuthorsW) and transfer the authorization back to the key diskette.

Transferring UCL licenses

To transfer the UCL license to the PLC, please use the "InstUCL.exe" program on the UCL license diskette.

Transferring licenses back to diskette

To transfer licenses from the hard disk back to the key diskette under Windows, please use the AuthorsW program on the SIMATIC NET CD.
It is not possible to transfer the license back to diskette or to check the licenses using the AuthorsW program on key diskette KV 5.0.

27 Requirements and Restrictions Relating to Hardware in General

The following CP 5613 names refer to the communications processors CP 5613, CP 5613 FO, CP 5614, CP 5614 FO, CP 5613 A2, CP 5614 A2 unless special types are named explicitly.

27.1 Note

Using ACPI (standby and hibernation mode)

Before you can use ACPI, you must first remove all modules and user programs (applications) from the Station Configuration Editor. If you use the CP 5613, further steps are necessary and you will be informed of this by a message displayed on your screen. ACPI functions are not supported by the CP 5613 communications processor.

Preventing a change to hibernation

When communicating via a SIMATIC NET module, your computer should not go into hibernation automatically.
You should therefore disable hibernation in the Control Panel -> Power Options -> Hibernate tab or put the module into configured mode.

Docking station operation

When a notebook is removed from the docking station, the configuration for SIMATIC NET modules is retained. When it is docked, the PC station no longer needs to be reconfigured and it is no longer necessary to download the STEP 7 configuration.

Follow the instructions displayed in conjunction with docking station operation.

Docking station operation is not supported by the CP 5613.

A single service for which the Station Manager waits during startup was not started.

The following entry can exist in the diagnostic information of the Station Configuration Editor:
"1 service(s) for which the Station Manager waits when starting up was not started."
This entry means that a function that must be processed before the Station manager starts was not completed.

This function might be the plug-and-play manager of the SIMATIC NET CD that looks for new hardware. If it is the plug-and-play manager, you can ignore the entry. This is then simply a delay and not an error. To check whether the plug-and-play manager is still running, follow the steps below:

Check the status of the service "SIMATIC NET P&PManager" in the services in the Control Panel of your operating system . If the status is still "Starting", the search for new hardware is not yet complete.

27.2 Computer Requirements

The products of this SIMATIC NET Software Products service pack were tested on PCs that meet the following minimum requirements:

· Pentium II-compatible CPU, 266 MHz

· 256 Mbytes of RAM

· To display the HTML documentation graphics card with a resolution of 800 x 600 with 256 colors

28 Compatibility

28.1 Operation with SIMOTION

SIMOTION V2.1 is not released for Windows XP/Windows Server 2003

SIMOTION V2.1 is not released for Windows XP and not for Windows Server 2003. For current information on SIMOTION products, please refer to the SIMOTION documentation.

SIMOTION V2.0 is not released with SIMATIC NET OPC V2.2 SP2 for Simotion.

Reason: With SIMOTION V2.0, only a hierarchical export is possible which means that browsing is no longer possible with SIMATIC NET OPC version V2.2 SP2 for Simotion (for example, incorrect variable information in the OPC SCOUT or ProTool/Pro-CS).

No OPC communication and configuration possible after uninstalling SIMOTION V3.0 SP1

After uninstalling SIMOTION V3.0 SP1, no OPC communication over the OPC scout or configuration using the Configuration Console is possible because the file melbreg.dll is deregistered in the system folder. To remedy this, (over)install the SIMATIC NET PC Software CD again.

OPC Data for SIMOTION

Please note the following constraints and functional restrictions:

· With asynchronous writes to a ReadOnly variable, no error message is returned although the value cannot be written and is not written. (synchronous write OK, here comes and error message.)

· Program variable of the type "DT" returns the value "00:00:00" when reading, this can, however, not be written.

· The invalid range of values of variables is not adhered to over OPC. Values can be written to variables that are outside the valid range.

· When writing to variables which the name "tracecontrol" or the name "internaltotrace", the error message "unexpected error in communication" is generated.

OPC Alarms and Events for SIMOTION

Please note the following constraints and functional restrictions:

· When you "export OPC data", only the diagnostic buffer entries specific to SIMOTION are exported and as a result a message text is returned over OPC only for these events.

· The OPC client that starts the OPC Server, also receives diagnostic buffer entries entered from this point onwards.

· Only one language setting for all clients:
Alarm texts are distributed to all clients in the same language (the language that was set last) even if you previously set different LocaleIDs.

· Maximum 40 Alarm_S permitted:
If more than 40 different alarms of the category Alarm_S are triggered in quick succession, only the first 40 will be delivered.

· Various SIMOTION diagnostic buffer events contain semantically incomplete texts. Here, Simotion SCOUT can add to strings that are not covered by the general syntax for process values.
e. g.:

"STOP by execution system, reason: Program missing for TechnologicalFaultTask", this event (text) is output as:

"STOP by execution system, reason: Program missing for" .
This applies to events with the IDs
F7678005 to F7676800C.

· Only one subscription possible:
If a client creates several instances of a subscription using the automation wrapper sopcdaauto.dll, the first subscription to be activated receives the events for both subscriptions; in other words, subscriptions activated later do not receive any alarms.

· If Alarm_S and Alarm_SQ arrive in fast succession and all alarms are acknowledged by the client, the following response can occur:

- Some Alarm_S alarms can be successfully acknowledged (incorrect), an acknowledgment event, however, does not arrive (correct).

- Some Alarm_Sq alarms cannot be acknowledged (incorrect), some Alarm_Sq alarms can be acknowledged (correct), an acknowledgment event, however, does not arrive (incorrect).

· Some parameter formats (parameter assignment in SIMOTION Scout with @...@) do not function as expected on the OPC Alarms and Events Server.

· Time stamp is changed: If the time zone of the client computer deviates from GMT, the OPC Server adds the difference between the local time of the client computer and GMT to the time stamps of the events. If there is daylight-saving time on the client computer, a further hour is added; Example: The module time is 11:33, the client works with CET (+ daylight saving), so the event has the time 13:33.

Workabout:

In the exported alarm XML file, it is possible to use a text editor to insert the parameter TimeDifference in the <HANDLERS> <SIMOTION> <DEVICES> node.

Example:

<Simotion_p

TypeID = "02D0A106-7ED2-4F92-B647-CB3B23097472"

CheckSum = 2002-10-29-09:11:44.175"

TimeDifference="-60"

MPIDefault = "2">

</Simotion_p>

</DEVICES>

The Alarms and Events calculates the time stamp of the alarm as follows:

Time stamp := (S7 time stamp on the hardware) + (time difference compared to GMT in min) – (value of the TimeDifference parameter) + (60 min, if daylight-saving time is set on the client computer)

The value of the parameter is therefore calculated as follows:

TimeDifference := (time difference compared to GMT in min) + (60 min, if daylight-saving time is set on the client computer)

Example:

The same time is set on the target hardware (S7 time) as on the client computer.

At the time the alarm occurs, CET plus daylight-saving time is set on the client computer; in other words, time difference = 60 min due to the time zone and 60 min due to daylight-saving time => TimeDifference="120". The OPC Server returns the time stamp that the alarm must have on the basis of S7 time.

· If you only export alarms during the OPC export in the SIMOTION Scout V2.1, an XML file is created. To make this XML file known to the OPC Server, a dummy file with the extension .SSD must be created in the same folder in which the XML file will be saved. This .SSD file is specified in the "Configuration Console" or in the "Commissioning Wizard".
As of SIMOTION V3.0, this dummy file is generated automatically during OPC export.

· If you disconnect the OPC client from the OPC server, wait at least 15 seconds before reconnecting.

No access to OPC_Data.sti during OPC export

Make sure that no other program accesses OPC_Data.sti during OPC export. To ensure this, you must close down all OPC clients. If the OPC_Data.sti file could not be written, the following must be done:

1. Close down the OPC client, for example the OPC Scout.

2. Delete the *.ssd- and the *.ldb file.

3. Start OPC Export again.

Access to SIMOTION projects

With SIMATIC NET, you can only access data of a single SIMOTION project.

Storage of the XML file

As of SIMATIC NET V6.1 SP1, the XML file exported by the SIMOTION Scout must be stored in the following folder on the destination drive in the installation path of SIMATIC NET:
<installation path of SIMATIC NET>\opc2\bins7\simotion\xml\opc_ae.xml

29 Notes on C Programming Interfaces

29.1 Note on all programming interfaces

Access points

If further modules are installed after installing the SIMATIC NET PC Software CD, the access points, for example, CP_H1_2:, CP_H1_3:, CP_L2_2: ..., must be entered manually.

29.2 Notes and Restrictions Relating to the SAPI-S7 Programming Interface

Connection reestablishment

Note that if a connection is aborted due to a problem (s7_receive = S7_ABORT_IND), the subsequent connection establishment with s7_initiate_req may only succeed after a maximum wait time of 90 seconds since the connection partner continued to occupy connection resources.

Reaction to error codes

If a function returns the value ERR_RETRY, the corresponding request must be repeated.

Example: s7_get_read_cnf = ERR_RETRY -> Repeat s7_read_req

Not all variable types

The variable types supported by the S7 protocol are at present not completely supported by all S7 servers (therefore the variable types STRING, TIMER, COUNTER and bit arrays should not be used).

Time until a timeout is reported

In the data transfer phase, the time required before an Abort indication is received is as follows for a CP 1613 with ISO:

· No data traffic	<	80 s
· With data traffic	<	8 s

Restrictions for SAPI-S7

The following functional restrictions apply to this version of the product.

Service/Function	Restriction
s7_get_vfd_ustate_ind	This service is not yet permitted.
s7_vfd_state_req	This service can only be used on other (remote) devices.
Variable services	The variable types supported by the S7 protocol are at present not completely supported by all S7 servers (therefore the variable types STRING, TIMER, COUNTER and bit arrays should not be used).

Multithread operation

Please note that the s7_receive( ) call and the corresponding processing function run in the same thread.

Autostart

Do not start an S7 application using the AUTOSTART program group,

otherwise you may encounter problems with the license server. When the computer boots,

the license server requires a certain amount of time before it runs.

s7_get_diag_ind returns incorrect diagnostic information

The s7_get_diag_ind function returns incorrect diagnostic information when fault-tolerant connections are operated over more than 1 user program (in the Station Configuration Editor of the PC station).

Remedy: Use only one application.

29.3 Notes and Restrictions Relating to the SEND/RECEIVE Programming Interface

Activating the trace

To activate modified settings for the trace, the SEND/RECEIVE user program must be restarted.

No data during connection establishment and termination using TCP/IP

During connection establishment and termination, no data can be sent or received by the user program when using TCP/IP.

User data

The components vc_buf1_ptr and vc_buf1_length are not supported in variable array 2.

No expedited data with TCP/IP

The following requests can only be used with the ISO protocol:

· SEND_EXP_DATA

· RECEIVE_EXP_DATA

"SEND/RECEIVE Programming Interface" manual

In contrast to the information in Section 5.5.1, pages 134 to 135, the conn_abort_timeout parameter specifies the maximum total time in units of 51 ms, the conn_persistence_count parameter specifies the number of repeated attempts during this time.

SEND/RECEIVE Programming Interface manual, Section 6.4 "Connection Establishment AWAIT_CONNECT_REQUEST (passive)"

Additional information on passive connection establishment, unspecified connection establishment. In this case, the length of the remote TSAP must be 8.

AWAIT_CONNECT_REQUEST_USER

In Section 6.5, the header return value for ok_decide_req_resp should be 1 (not 5 as described).

29.4 Notes and Restrictions Relating to the FMS Programming Interface

Manual "FMS Programming Interface, Section 3.8.5 "fms_get_report_ind"

The fms_get_report_ind service delivers the data in host representation. There is no network representation here.

30 Notes on Configuration, Configuring and NCM

Commissioning Wizard omitted and Station Configuration Editor expanded

With the SIMATIC NET PC Software CD 07/2001 and CD 11/2002, the Commissioning Wizard was installed automatically after installation of the PC software products and installation of the hardware modules. This has been replaced on CD 11/2003 by the expansion of the Station Configuration Editor.

You can now import the hardware and software configuration in the Station Configuration Editor using an XDB file importieren. This avoids the need to complete approximately 10 dialogs in the Commissioning Wizard. If there is no XDB file available, user programs or communication modules can also be inserted in slots of the Station Configuration Editor using the right mouse button.

After importing the XDB file, or inserting manually in the Station Configuration Editor, you can also download project engineering data.

PC Station Wizard

You can only use the SIMATIC NCM PC-PC Station Wizard to create a local configuration after inserting the modules in the Station Configuration Editor.

Complete description of the topic

The configuration of a PC using SIMATIC NCM PC and the related software is described in detail in the "Commissioning PC Stations" and "Industrial Communication with PG/PC" manuals.

Extra readme file for SIMATIC NCM PC

Please read the notes in the readme file for the product SIMATIC NCM PC on the SIMATIC NET Software Product CD or in the service pack download area.

Commissioning the PC with PROFIBUS network cards

As long as the configuration of the PROFIBUS network cards is not yet completes, the modules must not be connected to the network of the operational system!

When configuring a PROFIBUS network card, the station address, for example, must be set. Randomly set addresses can cause problems on the plant bus!

Downloading to a PC station using PC Internal

With certain network configurations, the following reaction can occur sporadically:
When downloading to a SIMATIC PC station using PC Internal, a message appears telling you that the system data block, for example, 1001 or 1007 cannot be deleted.
In this case, restart the download – and the download to the station will succeed.

Downloading to a PC station and avoiding modifications to the configuration

During a download from the SIMATIC NCM Manager, HW Config, or NetPro to the local SIMATIC PC station, make sure that no modifications are made in the Station Configuration Editor, for example deleting an application.

Dealing with problems when downloading or importing

Before downloading or importing configuration data, the "S7 Connection Diagnostics" program must be exited.

Error message immediately after installation

On some computers, the message "Application error caused a stack fault in module <unknown> ..." can appear immediately after installation and existing authorizations are not detected. To eliminate the problem, reboot your computer.

When downloading configurations, note the following:

User programs that do not communicate over the OPC interface must be terminated before downloading the configuration with STEP 7/SIMATIC NCM PC and then restarted.

Downloading or importing an XDB file of configurations with several hundred connections takes several minutes

Downloading or importing an XDB file of configurations with several hundred connections can take several minutes. Please wait until complete.

Configuring the "Access Point of the Application"

You can set an "access point of the application" both with the "Configuration Console" program and with the "Set PG/PC Interface" program. Never use both programs at the same time.

Configuration of the Information Service

When you install SIMATIC NET, an information service is installed that informs the user of special operating events. The events include the following:

· A trace is active for a protocol or a software component.

· An OPC protocol is deactivated.

The information service indicates the monitoring function with an icon in the status area of the taskbar.

A flashing warning triangle in the icon indicates a special operating event.

If you double-click on the icon, you open the window of the information service. Here, you will see the operating events listed. To read the detailed information of a message, click on the relevant row in the table of events.

You can close the information service if you are not interested in special operating events. Simply right-click on the icon in the status area of the taskbar and select the "Exit" menu command. The information service will then close down after a few seconds. It is also possible to restart the information service from the Start menu.

Configuration multilanguage setting Chinese

· Path names in Chinese characters are not accepted: When using multi-language operating systems with the basic language English and Chinese set as the current language, Chinese characters in the path names are displayed as question marks (?) in all edit fields in the "Configuration Console" (for example, trace file settings, symbol files).

· The information service is started with a larger character set, the horizontal scroll bar is therefore no longer fully visible.

Installing STEP 7 after installing the SIMATIC NET PC Software CD

If STEP 7 is installed after the SIMATIC NET PC Software CD and if the access point S7ONLINE is assigned to the CP 5613/CP 5613 FO/CP 5614/CP 5614 FO, the assignment must be confirmed explicitly in "Set PG/PC Interface" or the Configuration Console prior to communication.

Instance DBs are ignored on the OPC Server with S7 symbols

Instance DBs are ignored in the configuration of the OPC Server with S7 symbols in STEP 7 up to version 5.2.

Leading zeros when setting the access rights for OPC items

In NCM PC or STEP 7, you can restrict the access rights to OPC items in the properties of the OPC server.

Leading zeros in items and in the definitions are always ignored. For this reason, do not use placeholders "?" or "*" at positions at which a leading zero would be possible!

Example: The definition Slave0?9M06_AB1=R must be replaces by the following two definitions:

· Slave?9M06_AB1=R

· Slave9M06_AB1=R

Do not set CCAgent to "Pause"

After logging on, the "CCAgent State" dialog can be started in the information area of the taskbar. Do not set the "Pause" option. Otherwise, you can no longer start, log off or change user.

The WinCC process "CCServer" and "CCAgent" must then be exited by an administrator.

Diagnostic buffer entry in the Station Configuration Editor "The CP with index ... is not operational"

If the message "The CP with index ....is not operational" appears in the diagnostic buffer of the Station Configuration Editor, follow the steps below:

Change to network diagnostics of the "Configuration Console" program or "Set PG/PC Interface". Run diagnostics for the CP. The diagnostic information indicates the exact nature of the problem.

Diagnostic buffer entries when a download fails

In some situations, it is possible that a component rejects downloaded project engineering data. In such cases, the message "Module ... (index ?) in station ... cannot be started. Do you want to display the module status with the diagnostic buffer? Yes on no.". Please note that the diagnostic buffer cannot be displayed at this point. Use the diagnostic buffer of the target station.

After using the "Import Station" function often in the Station Configuration Editor, the Station Configuration Editor no longer responds

If you import XDB files often (using the "Import Station" function in the Station Configuration Editor), the Station Configuration Editor may no longer respond. The maximum number of imports depends on the number of components configured in the PC station. At the configuration limits, the maximum number is approximately 20. If the stations have less components, approximately 80 imports are possible. If this problem occurs, restart your PC. Following the restart, it is once again possible to import stations.

Error message in the diagnostic buffer of the Station Configuration Editor "The sdb is incorrect"

When importing XDB files ("Import Station" in the Station Configuration Editor), the message "The sdb is incorrect"/"component database is invalid" can be entered in the diagnostic buffer. If this problem occurs, it means that the project engineering configuration of your DP master system was not accepted. To apply the configuration, use the download function of STEP 7/NCM PC and download the PC station again.

Assignment of the CPs to the real hardware in the Station Configuration Editor

Following any change to the configuration (during station import etc.), please check the assignment of the CP modules in the Station Configuration Editor compared with the hardware installed in the PC; with PROFIBUS modules using their buzz functions if available.

To be able to assign a module uniquely when importing a station, the module type, module version, and the interface parameter assignment must match the settings of the existing real hardware exactly.

31 Examples of C Programming Interfaces

The best place to find examples of the C library interfaces is on the SIMATIC NET Quick Start CD Version 2, April 2000.

32 Development Environments and Compilers Supported

Compilers supported:

The following compilers can be used with the SIMATIC NET products under the following Windows operating systems:

· Windows XP, Windows Server 2003
- Visual C++ V6.0 SP5
- Visual Studio .NET, C++; with OPC also C# and VB.NET

- Visual Studio 2002, C++; with OPC also C# and VB.NET

- Visual Studio 2003, C++; with OPC also C# and VB.NET

· Windows 2000
- Visual C++ V6.0 SP5
- Visual Basic V6.0
- Visual Studio .NET, C++; with OPC also C# and VB.NET

- Visual Studio 2002, C++; with OPC also C# and VB.NET

- Visual Studio 2003, C++; with OPC also C# and VB.NET

Borland Compiler for Windows 2000

In cooperation with the AIXO company, an interface to the Borland Compiler is available. More information about the available Borland interfaces for SIMATIC NET products is available on the Internet http://www.aixo.com or by E-mail Info@aixo.com.

The required DLLs with Standard Calling Convention are no longer available in Windows XP/Windows Server 2003. To interface applications created with Microsoft Visual Basic or Borland Compiler, use the OPC interface.

Modified folder names

Please note that the folder names of the subfolders of simatic.net have changed compared with earlier versions with the introduction of the SIMATIC NET Software Products CD 07/2001. The extensions ".nt" and ".w95" are no longer used. As a result, you may need to adapt the path information for compiling your customer application.

33 Routing

New functionality: Routing

If you use this SIMATIC NET product on a PC/PG with a STEP 7/NCM PC V5 product, you can use the new routing functionality. For information on configuring, refer to the STEP 7 documentation.

What is routing?

As of STEP 7 V5, it is possible to reach S7 stations online beyond the boundaries of a subnet using a PG/PC, for example to download user programs or a hardware configuration or to run tests and diagnostic functions. You can attach the programming device at any point in the network and establish an online connection to all stations accessible via gateways.

Operating inter-subnet connections

As of version V6.0.5 of the SIMATIC NET PC software with STEP 7 V5.2/SIMATIC NCM S7 V5.2 or higher, it is possible to operate configured S7 connections over several subnets, for example from a PC on Ethernet over an IE/PB-Link to a PLC station with a PROFIBUS CP. Currently only configurations with one gateway and from Ethernet to PROFIBUS or vice versa are released.